I think there are a couple of thigs that need to be clarified here:
1) The controls from ISO 27001 Annex A and from ISO 27002 are the same; what is different is that ISO 27002 provides detailed guidelines on how to implement controls, and ISO 27001 does not have those guidelines.
2) ISO 27002 is not a mandatory standard if you want to get certified against ISO 27001. Or to be more precise, ISO 27001 does not mention that the control guidelines from ISO 27002 are mandatory. Therefore, the certification auditor cannot ask you to implement particular control in a way that is described in ISO 27002.
3) However, you need to implement each control that you consider is applicable, so unless you have a very good idea on how to implement that control you can use ISO 27002 as a guideline.
Information security management policy vs information security policy
Answer:
Yes, in the context of ISO 27001 this is the same document - such a document defines top-level management intent regarding information security and general roles and responsibilities.
Detailed security rules are usually written through detailed policies, for example in our toolkit you will see IT Security Policy that describes detailed general rules for all employees.
Risk likelihood
Answer:
First of all, you should record an incident in the Incident log, not in the Risk register - the purpose of Incident log is to record all the incidents from the past, while Risk register tries to anticipate the incidents from the future.
If an incident has already happened in the bust, then it has a much higher chance of happening in the future.
These materials will also help you regarding risk assessment:
- book ISO 27001 Risk Management in Plain English https://advise ra.com/books/iso-27001-risk-management-in-plain-english/
- Free online training ISO 27001 Foundations Course https://advisera.com/training/iso-27001-foundations-course/
Approach for the document management
1. Context – Read each template document to understand the context of each document.
2. Content – Replace the placeholder tags in the template documents with the relevant information as per the context of the document. Some of these information will be available in the current BCM document.
3. Compile – go through each document to check whether the document has no formatting issues.
What additional steps do we need to follow in addition to the approach described above?
Answer: Basically you are in the right way, but additionally, you can also define a method for the review and approval of documents. So, when you finish the documentation, some person can review each document (probably can identify some errors), and after a person can approval each document (if everything is ok). If after the review a change is necessary, you can also add this change in the change history.
It is also important to follow the sequence of folders for the implementation, because these are the optimal steps to implement the standard.
A third-party audit is performed by an audit organization independent of the customer-supplier relationship and is free of any conflict of interest. An audit by a regulator is independent of customer supplier relationship, and the audit organization is independent of the audited organization. So, an audit by a regulatory body can be considered a third-party audit.
The following material will provide you information about audits:
Usually controllers need to establish the identity of a data subject before answering any requests in order to ensure that they are dealing with the right person. However, asking you to provide a copy of your ID might be excessive especially because the EU GDPR does not apply exclusively to EU citizens.
La certificación e implantación de las norma ISO 9001 e ISO 14001 es igual para todos los sectores, incluyendo asociaciones sin ánimo de lucro, teniendo que dar cumplimiento a cada uno de los requisitos de las normas, como ocurre en el caso de una empresa.
Clause 8.2.3 is about the need to check if the organization has the capacity to fulfill a customer’s order. Clause 8.4.1 (last paragraph) can be interpreted, not mandatory, as a need to do supplier rating.
The following material will provide you information about relationships with customers:
Interfaces are the limit points between what is inside the ISMS scope and what is out (e.g., a website page is an interface between organization's information systems and the external public, a loading area is an interface between a supplier and the organization, etc.).
Dependencies are relations between organization's elements (processes, assets, etc.) that are needed to achieve a defined outcome (e.g., a datacenter depends upon a communication provider to make information systems available).