The standard requires organization to document a process (procedure) for ensuring that products are compliant with statutory and regulatory requirements related to the product in all countries in which the product arrives within its life cycle. This can be done in procedure for purchasing or in some separate procedure.
Legal requirements
Answer: If your organization must comply with this law then yes, compliance with it is a requirement for ISO 27001 certification.
Regarding if you should work first on the law or on ISO 27001, the first thing you should consider is the duration of your ISO 27001 implementation project and the deadline for compliance with that law. If your project can be concluded before the deadline, maybe it is better to start with ISO 27001 because, it can deliver an environment which can fulfil both, the law you need to be compliant with and other requirements your organization may have for the ISMS.
If your project cannot be finished before the deadline, you should consider if a reduction in the certification scope, e.g. to cover only the part of the original scope that would be related to the law yo u must be compliant with, can allow you to meet the deadline, and if postponing the implementation of the remaining scope is acceptable (since the management part of the system will be already implemented you will have less activities to perform).
If none of these alternatives are acceptable, then you should consider work first for compliance with the law, and after that make arrangements in the ISO 27001 implementation project to include those controls in the system.
Requirements from interested parties for working in public places
Answer:
Employee working in a public place is not an interested party, because he/she is part of your company - this person will have to comply with the security policies and procedures that your company develops. Therefore, the security requirements will come from within your company, n ot from an interested party.
En la caracterización de los procesos establezco las rendiciones de cuentas por los lideres de proceso, y en las juntas de calidad como los ejecuto?
Debo establecer una caracterización para la parte de liderazgo "Gerencia"?
Mi respuesta:
El análisis GAP puede ser una buena herramienta en la implementación de ISO 14001:2015 para enfocar el liderazgo y el compromiso de la alta dirección. Puedes considerar también el mapa de procesos existente para conectarlo con las responsabilidades de gestión documental para cada tipo de proceso.
En cuanto a la alta dirección o "gerencia", necesitará cumplir con los siguientes aspectos:
- Asegurar que los planes estratégicos de la organización y los objetivos son compatibles y están integrados, y que se encuentran dentro del alcance de la organización.
- Asegurar que los recursos necesarios están disponibles y que el SGA puede interaccionar con los procesos de negocio existentes.
- Adoptar la responsabilidad para de legar y dirigir empleados con el fin de asegurar que los objetivos de desempeño son cumplido.
- Asegurar que la mejora continua se alcance.
- Proporcionar liderazgo a otros puestos de apoyo dentro de la organización para asegurar que las metas generales son cumplidas.
- Comunicación: asegurar que los objetivos críticos, aspectos, y los parámetros de desempeño y resultados con comunicados de manera efectiva y continua a todos los grupos de interés.
P.S. we did a risk assessment for the IT-Services delivered and Chose the controls from A.15 for rist mitigation.
Answer: Even if your organization's IT operations are outsourced, some controls from section A.12 might still be applicable to it, like A.12.1.2 (change management), A.12.1.3 (Capacity Management) , and A.12.7.1 (Information systems audit controls), so you have to perform an evaluation first to verify this situation before consider all controls as "not applicable". For those t hat are totally under the provider control you can state them as "not applicable", providing as justification the IT operation is outsourced.
Regarding stating a control as "applicable" referring it to the ISMS of another organization, you cannot do that because you do not have control over provider's ISMS (at most you are an interested party - customer - that is considered in that ISMS context). For situations like that you can state controls from section A.15 as "applicable" to your ISMS, to ensure that the provider will take as much care of IT security as if you were performing the IT operations yourself. For example, if in your IT operations you would use backup practices, you have to ensure the service agreement also define that the provider also has I to use backup practices.
Answer: The first thing you should consider is the duration of your ISO 27001 implementation project and the deadline for EU GDPR compliance. If your project can be concluded before the deadline maybe it is better to start with ISO 27001 because, as you said, it can deliver an environment which satisfies GDPR and other requirements your organization may have for the ISMS.
If your project cannot be finished before the deadline, you should consider if a reduction in the certification scope, e.g. to cover only the part of the original scope that would be related to EU GDPR, can allow you to meet the deadline, and if post poning the implementation of the remaining scope is acceptable (since the management part of the system will be already implemented you will have less activities to perform).
If none of these alternatives are acceptable, then you should consider going first for EU GDPR compliance, and after that make arrangements in the ISO 27001 implementation project to include those controls in the system.
The organization needs to identify, document and maintain the alternate methods for process control and get approval from the customer for these controls. The list of alternate process control methods should be referenced in a control plan.
The standard requires documenting procedure for managing the use of alternate controls and this can be part of your production procedure, and standard work instructions are required for each alternate control.
ISO 31000 and ISO 27001
Answer: Yes, but as means to provide a common basis to align the information security risk management with other types of risk management in a company (e.g., quality risks, environmental risks, etc.). ISO 31000 by itself is not enough to comply with ISO 27001 because risk management requirements in ISO 27001 are much more detailed than in ISO 31000.
Answer: According ISO 22301, there is no requirement demanding such specific document, so unless defined by your organization, a law or another legal requirement, like a contract, you do not need to have it in your management system.
The business continuity life cycle is covered from standard's clauses 8.2 to 8.5, so, considering the list of documents that comes with your toolkit, you can share the following documents (of course the auditor can ask about the records related to these documents too):
Business Impact Analysis Methodology
Business Continuity Strategy
Business Continuity Plan
Incident Response Plan
Disaster Recovery Plan
Exercising and Testing Plan
BCMS Maintenance and Review Plan