Answer:
The relation between ISO 27001 and ISO 27002 is simple: ISO 27001 establishes requirements for an Information Security Management System, and includes the Annex A with 114 security controls. ISO 27002 is a guide of best practices for the implementation of the 114 security controls of the Annex A of ISO 27001.
Really you only need to implement the necessary security controls after the risk analysis, and you will nee d ISO 27002 only if you need specific information about how to implement the security controls of Annex A of ISO 27001. This article can be interesting for you “The basic logic of ISO 27001: How does information security work?” : https://advisera.com/27001academy/knowledgebase/the-basic-logic-of-iso-27001-how-does-information-security-work/
Answer:
I am sorry but you cannot implement CISA in a company because it is only a certification for people. Regarding COBIT, this standard is focused on IT governance, which also includes the information security, but has a different objective.
So, if you need to manage the information security, the best standard from my point of view is ISO 27001, because is specifically developed for this, while COBIT is developed for IT governance.
Answer:
ISO 27001 is the lead standard about the information security, and most of laws and regulations about information security of all the world are based on this standard.
COBIT is focused on IT governance, which also includes information security, but ISO 27001 is more specific.
Regarding COSO, this standard is also for different things: internal control, event identification, risk assessment, etc. So, again, this standard is not specifically developed for information security.
So, if you want to establish an Information Security Management System to protect your information, the best option, from my point of view, if the ISO 27001.
Answer:
There is an ISO standard specifically related to the information security control for cloud services (or cloud computing environments): ISO 27017.
This standard is a code of best practices, but there are some certification bodies that offer a certification if the company comply with a series of requirements based on the standard.
Answer:
I am not sure if I have understood your question, but if you want to obtain the support from the management to implement an Information Security Management System in your organization (based on ISO 27001),it is very important to show them the benefits of the implementation of the standard, which basically are: compliance, marketing edge, lowering the expenses, and putting your business in order. This article can be interesting for you “Four key benefits of ISO 27001 implementation” : https://advisera.com/27001academy/knowledgebase/four-key-benefits-of-iso-27001-implementation/
Answer:
To comply with the clause 9.1 basically you need to perform a monitoring, measurement, analysis and evaluation of your ISMS. How can you do this? A way is using metrics. An example:
If an objective is to reduce backups failures (10%), you can perform a periodic measurements (for example each week) with this formula: Failure backups / Total backups. And you can see how is the evolution of the measurements.
Another example can be to reduce the number of unauthorized access to a critical server (15%), so you can use this formula : Unauthorized access / Total access. And see the evolution performing periodic measurements.
Answer: ISO 27001 does not require you to separate password policies for different types of users/employees - therefore, you can create a single document for this purpose. In bigger and very complex companies it might make sense to have separate policies for this purpose.
Also, if there are 10 sites in the scope of the certification audit, so at the time of surveillance audit (how can auditor do sampling of site i.e. what to include and what not).
Answer: If you are asking about the surveillance visit that is performed by the certification auditor, then this is the decision made by the certification auditor, not the company that has the certificate. They make such decision based on the importance of particular sites, and based on the fact where did they find most of the nonconformities during the previous visit.
When determining what parts of your company should be a part of your quality management system, you need to look first into the reasons for implementing the standard. Is is the requirement of the customer, is it a condition for applying to tenders or is it a requirement of the company itself? The answer to this question will shape the scope of your QMS.
If it is a requirement of the customer and it only refers to a product produced on only of of your production lines, you might decide to include in the scope only that production line and leave others from the scope, the same can be applied in case of tenders as well. If it is a requirement of the company itself, it is most common to include the entire company in the scope.
Regardless of the reason for implementing ISO 9001, you might choose to implement it in only several processes in the company, on one ore more location where your company has branches or to cover one or more production lines and yet not to cover entire organization.
Reasons for limiting the scope to only a part of the company can be to decrease the price of implementation and certification of the system or to cut the time of implementation.