Answer: I'm assuming you are referring to European 2017 Revision of ISO/IEC 27001. Considering that, this is an European version of ISO 27001, with minor adjustments that do not affect an ISMS based on ISO 27001:2013, so there are no corrections needed on documents from the toolkits.
2. Also regarding the risk assessment and treatment should not be signed from risk owner and others? Please advise or any recommendation whom shall sign?
Answer: The residual risks, final result of risk assessment and treatment proc ess, must be accepted and signed either by risk owners or by top management on their behalf. What normally happens is that top management formally accepts residual risks and only consult risk owners on situations where residual risk is not clear enough and requires clarification (e.g., when a residual risk has high value and the treatment option chose was accept the risk).
3. And also in case of the organization has ERM section or department how it will be handled shall information security department ignore ERM and follow this methodology? Keep in mind the organization are adopting ISO 31000 and framework are defined is it better to refer to them?
Answer: First it is important to note that ISO 27001 does not prescribe a risk assessment and treatment methodology, so an organization can adopt the methodology that best suits its needs. Additionally, the standard provides a note informing that its requirements aligns with the principles and generic guidelines provided in ISO 31000, so you can adopt the methodology used by the ERM section, only considering minor adjustments for it to consider relevant aspects for information security.
If this activity is considered critical to the business, and its disruption for an amount of time can make business unrecoverable, then you must include it in the BC. The difference from this activity to the others is that while for others activities you may have to consider recovery on a daily time frame (i.e., in the next day the activity will be required), for this specific activity you have to consider a weekly time frame for recovery (if not recovered on Monday/Tuesday, the activity will be required only on the next week). On both cases you have to consider worst-case scenario, i.e. that the disruption occurs at the worst possible moment.
Answer: ISO 27001 does not prescribe any record to be in both; electronic form and paper form, so the only justification for keeping a record in both formats is if you have business or legal requirements demanding this specific situation. If such requirements do not exist, then you can keep a record only in electronic form.
2. Is it allowed to have all records in electronic form?
Answer: Considering answer 1, if you do not have business or legal requirements demanding records in paper form, you can keep all records in electronic form.
3. Security Procedures for IT Department, Erasure and destruction records; commission for the destruction of data: Is it okay to write "Records of erasure/destruction must be kep t for all data that is stored on the server" (as an example) if I'm not implementing the Information Classification Policy?
Answer: In theory this is acceptable, but without information classification levels to decrease the need for such erasure and destruction records you may end up with an effort greater to keep such records than the effort to administrate classification levels and adopting an Information Classification Policy.
4. Are there any specific requirements we must fulfill in order to have an adequate Training and Awareness Plan? Since the datacenter is the only location in the scope and it has adequate protection and security, I don't see a specific subject which the employees could gain knowledge about. All of them know the basic security principles, aside of that they have a good understanding of how to assign and revoke access rights and such. A presentation concerning Security Awareness Training could be attended, but this would also include specific elements which are not relevant in the context of the scope.
Answer: Training and Awareness Plan objective is to help ensure persons are competent on the basis of appropriate education and training, by mapping gaps to be eliminated, so if your organization identifies that employees in the ISMS scope already have an acceptable level of competence, you can minimize the content of the plan (e.g., consider only awareness communication and recycling training).
5. Training and Awareness Plan: "the following awareness-raising methods must be applied: information day, intranet articles, newsletter, joint meetings, e-learning, internal e-mail messages, video recordings.". Is it possible to adjust this list? We don't 'need' all of these in order to ensure that everyone has the adequate knowledge and skills.
Answer: The list provided in the template is only a suggestion, so you can adjust it according to your needs, including or excluding activities.
6. Confidentiality Statement: Is it mandatory to implement this document? We do have our own NDA, but this does not cover labeling.
Answer: The confidentiality statement template included in the toolkit is not required if your organization already makes use of an NDA document, but if control A.8.2.2 Labeling of information is applicable, then you may have to adjust it so it is clear in the NDA how people can identify information classification levels, and thus handle information properly.
7. If the unacceptable risks for a particular control are being transferred to a third party, what do we write for this control in the Statement of Applicability? Technically there are unacceptable risks for the control (so I don't think we can state that there are no unacceptable risks), but they are being transferred.
Answer: In the scenario you stated, you must write that the control is applicable because there are unacceptable risks demanding its implementation, and in the implementation method column you can write that the defined treatment for related risks is "risk transfer" and that this control is being implemented by a third-party.
Gathering information from suppliers
What are the mandatory resources need to collect for review/risk assessment purposes from application supplier/vendor?
Answer:
In a general manner you have these options to consider:
- Propose to sign a Non Disclosure Agreement to have access to their policies
- Ask for a general view only of these policies to see if they can fulfill your needs
- Ask them about how they handle your specific risks related to this critical application
If none of these alternatives are possible, you should consider if the risk of taking over the application without these information is acceptable, or if you should consider another supplier for this application.
Regarding mandatory resources to collect, ISO 27001 is not prescriptive. The information you will need will depend on the results of risk assessment and legal requirements your organization has to fulfill.
Based on risk assessment and legal requirements you can sign a service agreement with this supplier including security clauses that specify if the access to documentation is needed or not.
The first step to develop polices and procedures is to identify which requirements the policy or procedure must fulfill. For example, your organization may have contracts, laws, or regulations with clauses defining a specific approach for a governance solution. After identifying those requirements you should consider the context of your organization regarding size, processes complexity, and staff maturity.
A ISO 27001 não prescreve nenhum conjunto específico de nomes para uma organização usar, então elas são livres para adotar o esquema que melhor lhes convier.
Os documentos do kit estão organizados em pastas com nomes e em uma sequência didática de implementação que você adotar para a sua estrutura de arquivos.
Para entender os termos usados pela ISO 27001, sugerimos que você dê uma olhada na ISO 27000, que fornece visão geral e vocabulário para segurança da informação, neste lin k: https://www.iso.org/standard/73906.html
A partir desta norma, você pode encontrar termos que você pode aplicar em seu esquema de nomenclatura.
People and clause 7.1.2
Answer:
The standard requires that an organization has the persons considered necessary to effectively operate and control the quality management system.
For example, a hotel may establish that breakfasts must be serviced by different number of employees as a function of number of guests, a hospital may establish that a certain service must has a certain composition in terms of number of persons and professional categories, a long distance bus company may establish a crew composition as function ok kilometers of the service. In other cases, legislation or regulation may establish a number of persons performing a role and their qualification.
Answer:
When I work with organizations in determining their risks, I use three perspectives:
I consider ISO 9001:2015 clause 4.4.1 – what can go wrong in each process
I consider ISO 9001:2015 clause 5.1.2b) – what can go wrong with products and/or services
I consider ISO 9001:2015 clause 6.1a) – what can go wrong with our intended QMS results, QMS objectives.
“Some managers even ask if quality objectives are the same as the performance objectives.”
Answer:
Yes, one can say that quality objectives are performance objectives.
“Can one process be used to meet several objectives.”
Answer:
Yes, one process can be instrumental to meet more than one objective. I like to make the relationship between objectives and processes very clear. That is why I recommend using a matrix like this one:
This way one can find that currently there is no process in place that can help the organization to meet Objective A, and that Processes 1 and 3 do not contribute to any quality objective.
“What is the main difference between process approach and risk management many people ask me.”
Answer:
The matrix above is a representation of the process approach. The intended results of an organization will be met through processes. There are no random results. If we don’t like current performance, we should act upon what we do, one or more of our processes. That is why in Quality there is the saying: Don’t blame the product (the result), blame the process (behind it). Risk management is about determining risks, evaluating them, deciding if some of them are significant, and act to reduce, control or eliminate those significant risks.
ISO 9001 and documentation for a Construction Company
Answer:
I recommend you start describing how the company works as a set of processes. Then, relate those processes with ISO 9001:2015 clauses
When implementing a QMS I see it as a project with two work fronts: A and B.
A is about modeling how the organization works based on what is called the process approach. Describing an organization as a set of interacting processes.
See this generic example:
Then, for each process look for what can go wrong and should be improved, look for opportunities to take advantage, and see if ISO 9001:2015 requirements are already being met. Describe those processes in order to standardize your work.
B is about where is the organization going to. It is about strategic orientation, objectives and plans to meet them. It is about overall risks and opportunities and what to do to manage them.
“(2) How to define SOPs, KPIs and necessary documents?”
Answer:
ISO 9001:2015 clause 4.4.2a ) gives a lot of freedom to organizations about which documents to create. That will be a function of the complexity of your organization, of the experience and turnover of your employees, of the requirements of customers, and current performance challenges.
This website stores cookies on your computer. These cookies are used to collect information about how you interact with our website and allow us to remember you. We use this information in order to improve and customize your browsing experience and for analytics and metrics about our visitors both on this website and other media. To find out more about the cookies we use, see our Privacy Policy.
If you decline, your information won't be tracked when you visit this website. A single cookie will be used in your browser to remember your preference not to be tracked.