Answer: ISO 27001 does not prescribe which criteria to use to define conditions for document review, so you can use only the review "if necessary" conditions. However, it is a good practice to define a time frame, so you can ensure that documents are reviewed before events that have a time frame defined (e.g., you have to define a time frame for the management review and this review has inputs that can lead to the need of documentation review).
The requirement you refer to is meant to be complied with the data processor that is processing personal data on your behalf so, any of your processors would need to have at least a security policy in place to protect personal data. Of course a supplier can have a whole security framework in place with a multitude of documents.
As for you own security setup you can find a couple of security related policies in folder 8 of our EU GDPR implementation toolkit https://advisera.com/eugdpracademy/eu-gdpr-documentation-toolkit/ , from which you can choose which is most relevant in terms of your business activities. I can also warmly recommend ISO 27001 as a good example of a security framework.
There are six legal grounds for processing which can be found a article 7 of the EU GDPR (https://advisera.com/eugdpracademy/gdpr/lawfulness-of-processing/). These six legal grounds are:
- Consent - The individual has given consent to the processing for one or more specific purposes;
- Necessary for performance of a contract - The processing is necessary for the performance of a contract with the individual or in order to take steps at the request of the individual prior to entering into a contract;
- Legal obligation - The processing is necessary for compliance with a legal obligation to which the controller is subject. Only legal obligations under Union or Member State law will satisfy this condition. However, that law need not be statutory (e.g. common law obligations are sufficient);
- Vital interests - The processing is necessary in order to protect the vital interests of the individual or of another natural person . This is typically limited to processing needed for medical emergencies;
- Public functions (public interest) - The processing is necessary for the performance of a task carried out in the public interest or in the exercise of official authority vested in the controller. Those functions must arise under Member State or EU law; or
- Legitimate interests - The processing is necessary for the purposes of the legitimate interests pursued by the controller or by a third party, except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject which require protection of personal data, in particular where the data subject is a child. Public authorities cannot rely on this condition.
Answer:
ISO 20000 contains many required records ,documents or other information. So, it's hard to generalize. In e.g. Incident Management or Change Management processes - you will look for tickets related to incidents i.e. changes. Same for Problem Management. Availability or Capacity Management will require measurements - so you'll look for measurement files.
Further on, Configuration Management requires CMDB. So, you need to check whether it exists, in which form, does it fulfill standard's requirements...etc. CIs need to have recorded incidents and changes...so, these are all items you need to check.
Pregunta: He estado trabajado con la documentación que me enviaron, sobre todo con la del BIA, pero ahora necesito abordar el tema de la comunicación cláusula 7.4 de la norma, tienen documentos para este punto, no lo he podido identificar en el pack de documentos.
Respuesta: Puedes cubrir todas las cuestiones relativas a las comunicaciones con el Plan de Respuesta a Incidentes, el Plan de Continuidad de Negocio, y el Plan de Recuperación. Por tanto, básicamente no tenemos un documento específico para la cláusula 7.4 de la ISO 22031, pero puedes usar los documentos que he mencionado para cubrir con los requerimientos de esta cláusula.
Implementation of knowledge management?
Answer:
You should determine the knowledge that your organization needs to operate their processes and make products and services according to requirements.
You should maintain this knowledge and make it available as needed, for example, when new people are contracted.
Consider your current knowledge when making changes, and determine how you will gain additional or updated knowledge if necessary for the changing needs.
The following material will provide you information about knowledge management:
There are no mandatory documents required by ISO 9001:2015 to evidence implementation of Risk Management.
So, you are free to decide how to perform and evidence Risk Management. Normally, organizations create a non-mandatory procedure for addressing risks and opportunities, and generate a Risk Registry to keep a list of updated determined risks and opportunities, their evaluation according to action need; the actions performed and the evaluation of their effectiveness.
The following material will provide you information about the risk-based approach:
Will the acquired company be merged with your organization with the same brand(s) and logo? If yes, your organization is changing the scope of the management system with a new geography/site. In that case your company should contact the Certification Body to inform them about the change.
The following material will provide you information about the management scope:
Thanks. All very good advice and I will follow it up.
EU GDPR for the banking sector
Answer:
There are no specific DSGVO (EU GDPR) for the banking sector alone, the GDPR is meant to be applicable across industries as long as personal data is being processes. The same is applicable for software development.
Another thing you should consider, if your software is front facing the data subjects, it is the notices you would have to present to the data subjects. Guidance on the notices can be found in folder 2 “Personal data policy framework” in our EU GDPR toolkit https://advisera.com/eugdpracademy/eu-gdpr-documentation-toolkit/
Don`t forget also local banking sector specific requirements that might be applicable for banking software especially in terms of security.