Answer: ISO 27017 and ISO 27108 only provide recommendations and guidelines to the implementation of controls of ISO 27001 Annex A, so their application is not mandatory for an organization to be compliant with ISO 27001.
Regarding if you can skip cloud elements until the implementation of ISO 27001, you can only do that if there is no cloud-related elements on your ISMS scope.
This gap analysis tool is a simple question-and-answer checklist that will help you identify which specific elements of ISO 27001 you’ve already implemented, and what you still need to do.
Mapa de procesos
El enfoque basado en procesos es uno de los principios más relevantes en ISO 14001, y el mapa de procesos forma parte de ello. Un buen mapa de procesos debe de contener todos los procesos dentro de la organización clasificado por tipo y orden de ejecución, lo cual proporcionará con una visión general de todo el sistema de gestión.
La responsabilidad ambiental es el principio más importante de un SGA, así que el mapa de procesos puede ser empleado para demostrar el control del impacto ambiental de los productos, servicios u operaciones de la organización.
Para asegurar que se conocen los límites de lo que tiene que hacerse, es necesario definir el alcance del SGA. Esto ayudar a prevenir la inclusión de áreas de negocio que podrían no afectar al medio ambiente. Para determinar el alcance se deben de considerar:
- Cuestiones internas y externas mencionadas en la sección del contexto de la organización: Ambas deben de considerarse para asegurar que el alcance es definido correctamente y que el SGA es efectivo.
- Obligaciones de cumplimiento
- Unidades de la organización, funciones, límites físicos
- Actividades, productos y servicios
Las herramientas clave para definir el alcance son la política ambiental y los aspectos ambientales (la interacción que la organización tiene con el medio ambiente); estos son los primeros documentos que necesitan crearse para el SGA.
Para más información, vea los s iguientes artículos:
Answer: In the root folder of the toolkit you'll find a document called “List of Documents” which will explain which control is covered by which document. In there you will find that control A.11.1.5 (Working in secure areas) is covered by template "Procedures for Working in Secure Areas", that can be found on folder 08 Annex A A.11 Physical and environmental security.
Regarding the other controls from section A.11.1, ISO 27001 does not require a document for each control that is implemented. For small and mid-size companies generally is sufficient to simply describe how they are implemented in the Statement of Applicability (SoA). This template you can find on folder 06 Statement of Applicability.
The clause 8.5 is referring to the products and services equally. Although you deliver service and not the product, you will have to comply with most of requirements from clause 8.5. Considering the type of business you are in, I would suggest you the following exclusions:
- 8.5.1 f) - validation of product and service
- 8.5.2 Identification and traceability
- 8.5.3 Property belonging to customers and external providers
- 8.5.4 Preservation
- 8.5.5 Post-delivery activities
Of course, you will have to provide justifications for the exclusions and keep in mind that I'm not 100% familiar with your processes, so you will have to check if all these exclusions are possible. The rest of the requi rements in clause 8.5 will apply to your organization.
Answer:
Problem Management KPI's can relate to problem's, incidents and changes. Here are few examples of PM KPI's:
Number of recurring incidents
Number of incidents without permanent resolution
Number of available Known Errors
Total numbers of problems
Size of current problem backlog for each IT service
Number of opened changes as a result of root cause elimination
It seems to be very similar : Studying the issues or risks that are related with our context and our organization.
Also how to demonstrate that ? Make a list ? a table ?
At the scale of a worldwide group, it can be harmonised right ? or at least there be a general basis that the plant can personalized I think.
Answer:
Risk and opportunities and external and internal issues are fundamentally different. Issue is a source of the risk or opportunity but it is not a risk or opportunity by itself. For example, old equipment is the internal issue, but the risk related to it are frequent malfunctions, halts in production or inefficient energy consumption. On the other hand, government that is willing to invest in eco-friendly projects is an external issue, the opportunity related to it can be to get funding to renew or update the equipment used by the organization.
The issue, whether it is internal or external is just a fact about the conditions in which the organization operates, while risks and opportunities are positive or negative effects that can occur regarding the issue. For example, coffee is hot, but that alone is not a risk, it is what we do with the coffee what increases risk of getting burned.
The standard doesn't require internal and external issues to be documented, however it requires risks and opportunities to be addressed to be documented and this can be done with list or register of risks and opportunities.
As far as the context goes for the worldwide corporation, you can define one global context of the organization and define more detailed context for smaller organization units on the level of countries. There can also be a list of risks and opportunities on global level and the risks and opportunities on local or country level, since the context in every country can be different to some extent and therefore the risks and opportunities.