There is no requirement in the standard to update the risk assessment on a periodic basis. Nevertheless, a company can decide to update the risk assessment based on the calendar. Another possibility is to update the risk assessment based on nonconformities occurrence (see clause 10.2.1 e)) or after reviewing information about internal and external issues (see clause 4.1), or about interested parties (see clause 4.2).
The following material will provide you information about risk assessment:
Supporting functions, whether onsite or remote ( such as design centres, corporate headquarters, and distribution centres) should be included in the Quality Management System. you need to include all of them if they are part of your company. Auditing just a corporate headquarters won't provide evidence that you company is fully compliant with the standard, all processes and functions need to be audited.
First of all, you should note that threats in ISO 27005 catalogue are only examples. They are not mandatory, and probably your organization will have some threats that won't be there (you have to identify them by performing the risk assessment process).
That said, to identify if a threat is related to confidentiality, integrity or availability, you have to analyse how the threat will work over an asset. For example, a malicious software can either allow an unauthorized person the access an information in a database (compromising confidentiality), change it (compromising integrity), or destroy it (compromising availability). This will depend on how the malicious software work.
In case of embezzlement, it is, by definition, a financial fraud (a fraudulent conversion of the property of another person by the person who has lawful possession of the property). Basically this threat is related to the information related to the ownership of a property, then it can be r elated to compromise of information integrity, since in many times involves falsification of records in order to conceal the activity.
Yo can use the general framework and adapt to your needs. For example, you can change the following information:
- "what ISO 27001 is all about" to "what ISO 22301 is all about"
- "why is it good for the company – and also for themselves" to "why BCPs are good for the company – and also for themselves"
- "what is their role in handling information security" to "what is their role in BCP"
Then you can finish presenting the BCP.
Have you written a blog post that could help me and I’m sure others understand the boundaries of an ISMS scope.
Answer: The first thing you need to identify for the scope's limits is to understand the organization's purpose for its ISMS and the requirements this ISMS has to fulfill. Once you know that you can identify how each department you mentioned is related to this purpose and requirements and then you can define the scope limits.
Examples of limits for the scope related to Finance and HR may be:
- Financial reports deemed for regulatory bodies (e.g., as required by SOX)
- Employees' and customer's medical records (e.g., as required by HIPAA)
For IT departments, the scope could be limited to information systems used by Financial and HR departments.
Answer: Conformio does not have a separate module for risk management, however if you go for the Startup Plan, you will get the ISO 27001 Documentation Toolkit which will enable to you to perform the risk assessment and treatment using the Word and Excel files.
Among other templates, this toolkit contains the following documents: Risk Assessment and Risk Treatment Methodology, Risk Assessment Table, Risk Treatment Table, Risk Assessment and Treatment Report, Statement of Applicability and Risk Treatment Plan. They can help you cover ISO 2700 1 requirements regarding risk management.
ISO 27002 corrigendum related to change of control objective A.8.1.1 in ISO 27001 does not add any clarification regarding the meaning of information. It only makes texts adjustments regarding the change of control objective. To see this related corrigendum, please access this ISO page: https://www.iso.org/obp/ui/#iso:std:iso-iec:27002:ed-2:v1:cor:1:v1:en
In fact, ISO 27001 series do not define the meaning of information, allowing organizations to use the definition considered more appropriate to their context. So, my recommendation to you is that your organization document a definition for information that is adequate to its context and implement its controls according this definition.
ISO 27017, ISO 27018 and ISO 27001
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.