Risk assessment and application control practical examples
a. Risk Assessment Table
b. Risk Treatment Table
Answer: Together with the ISO 27001 Documentation Toolkit you bought you have access to video tutorials with practical examples that will help you fill the risk assessment and risk treatment tables. In those videos you will get examples of vulnerabilities, threats, and how assess the level of risk, as well as how to determine options for the treatment of risks and appropriate controls for unacceptable risks.
2. A file (cross-link) that defines the 27002-controls that should be used for the pre-defined vulnerabilities as used in the template that is part of the toolkit.
Answer: Since the applicability of ISO 27002 controls is unique for each organization's context, even for the pre-defined vulnerabilities listed in the template, we do not provide definitions on what should be used by organizations (this is an organization decision, based in specific information). What we can provide are criteria and recommendations that should be considered when deciding which treatments and controls to apply through our many blog post you can consult here: https://advisera.com/27001academy/blog/
If you still feel you need more assistance you can schedule a meeting with one of our experts to ask for more specific orientation (https://advisera.com/27001academy/consultation/), which is also part of the toolkit you bought.
Business continuity strategy, plan, and procedure
Answer: The business continuity strategy is related on how an organization will ensure its recovery and continuity in the face of a disaster or other major incident or business disruption. It covers general decisions applicable to a wide range of types of disasters, major incidents or business disruptions (e.g. use of alternative sites).
The BC plan defines precisely how the organization will manage incidents in the case of a specific disaster or other disruption of business, and how it will recover its critical activities within set deadlines (e.g. BC plan for chemical leakage, fire, etc.).
The BC procedure is a document defining how a specific business continuity activity should be performed (e.g., evacuation procedure).
But how bcp is done in sectors like Manufacturing , Petroleum or Aviation , we cannot really have redundant Plants of manufacturing or those units for petroleum . So in these industries how bcp is done , where does bcp play role in these industries , how business continuity is implemented in sectors like aviation , what value does business continuity bring to these mentioned industries.
Answer: Yes, you cannot have redundant manufacturing plants or petroleum platforms, but you can have as many redundant valves, pipes, and other critical elements, which a Business Impact Analysis and a Risk Assessment identify as necessary to avoid a situation to reach a level so critical as to compromise the entire facility. That's why, for example, a plane has secondary, tertiary, and even quaternary systems, to avoid a failure th at can make the plane crash.
So, not only in these, but in all industries, the business continuity management helps identify and implement business continuity in a cost effective way by identifying the balance between the smallest set of critical points that must be protected to achieve the greatest protection level.
Answer: No, on the contrary, you should seek to integrate the systems. Since 2012, all released ISO management systems standards have the same basic structure, which makes easier to integrate them. By doing so you can save administrative effort in such areas as document and record control, internal audit, performance monitoring, measurement and evaluation, and improvement.
(What is the approximate value to implement ISO 27001 in a logistical evaluation support center in Colombia?)
Answer: There are a significant number of variables to be considered when estimating an implementation cost, so without more detailed information it's not possible to precise a value.
What I can tell you are some cost issues you should consider:
- Training and literature
- External assistance
- Technologies to be updated / implemented
- Employee's effort and time
- The certification process
Answer: The information to be stored will depend on the results of risk assessments, applicable legal and contractual requirements, and any other decision made by the organization regarding the project. Applying information security in project management is like implementing a small and simplified version of an ISMS in the scope of the project.
There are many similarities with implementing an ISMS that you can use to drive the implementation of information security in project management:
1 – You have to define information security objectives and include them in the project objectives, the same way you define information security objectives for an ISMS aligned with organization's objectives, the only difference is that these objectives are restricted to the scope of the project.
2 – You have to perform at the beginning, and periodically, information risk assessments in the project, like you would do it with other bu siness processes, to identify necessary controls
3 – You have to ensure that information security practices are part of all phases of the project (e.g., from the issue of the project charter to project closing).
In short, you can think the inclusion of information security in project management as if you are going to implement a small ISMS that will fit the projects needs and be proportional to the project's lifetime and budget.
This article will provide you further explanation about information security in project management:
- How to manage security in project management according to ISO 27001 A.6.1.5 https://advisera.com/27001academy/what-is-iso-27001/
Answer: Yes, the latest revision of the ISO 27001 & ISO 22301 Premium Documentation Toolkit is the 3.1, published in 2015
By the name of the documents you provided, it seems to me you are comparing the white paper "Checklist of mandatory documentation required by ISO 27001:2013", available as free download at https://info.advisera.com/27001academy/free-download/checklist-of-mandatory-documentation-required-by-iso-27001, against the List of Documents file from the toolkit you bought, and you shouldn't do that. You should follow the information in the list of documents file in your toolkit.
2- Also, the Business continuity procedures is not required or used in the new version; however, it is required in the 2013 version.
Answer: This toolkit is fully compliant with ISO 2700 1:2013 and ISO 22301:2012. The requirement for businesses continuity procedures is covered with the Disaster Recovery Plan in the ISO 27001 Documentation Toolkit.
3 - Is the Supplier security policy no longer mandatory?
Answer: Supplier security policy is mandatory only if the results of risk assessments identify that there are unacceptable risks that can be treated by this control, there are legal or contractual requirements that demand the control to be applied, or if the organization has a recorded decision to apply this control. Besides these reasons, an organization is not obligated to implement a supplier security policy.
SoA content
From the standard, I am not able to gauge whether the above fields are mandatory.
Answer: The justification for inclusions is needed because the reason for applying a control will help understand how to evaluate its effectiveness. For example, if the reason is because results of risk assessment, them we have to check which risks are being treated by the control to ensure all of them are being handled properly. On the other hand, if the reason is because of a legal or contractual requirement, we need to identify if this requirement is being properly fulfilled
You can find the requirements for filling the SoA in the clause 6.1.3 d) of ISO 27001.
This document provides a list of questions in order to help perform an internal audit against ISO 27001, so you can verify compliance with standard's requirements and applicable controls.
Answer: Yes, according ISO 27001, you have to document operational planning and control, but the extent of what will be documented is up to what the organization decides as sufficient to ensure the processes are being performed as planned. In our experience, some controls require more detailed documentation than others, but in general there is no need for a 'manual' to centralized them all.