If you have persons trained as Lead Auditors 14001, you have persons that know how to perform an audit. Do they know ISO 9001? What are the organization requirements for internal auditors? Are they required to evidence knowledge of ISO 9001? Can they evidence it?
The following material will provide you information about Internal Audits:
While the organization has a number of security controls in place, they have a significant lack of documented policies, standard, and processes/procedures. We are not specifically calling out in the risk assessment the lack of documentation, and maybe we should.
When completing the risk assessment, I believe we are closely following the advice from the videos and blogs on your site. For example, rather than listing out all of the assets during this initial risk assessment, we are grouping the assets into “asset categories” where very similar assets will have the same threat & vulnerability pairs. We are selecting 2 or 3 threats for each asset and 2 or 3 vulnerabilities that can act on each of those threats. Due to existing controls (while undocumented ), the subject matter experts are categorizing many of the risks as acceptable (score of 0, 1, or 2) and only about 25 of the risks as unacceptable (score of 3 and 4).
When moving from the risk assessment to the risk treatment, I am a little confused. We intuitively know that the organization expects to have 107 of the 114 ISO 27001 controls in place when the project is complete. They are using many of those controls today. However, as I mentioned, the organization has a significant lack of documented policies, standard, and processes/procedures.
How do I create the association between the risk assessment and the controls selection when there are only about 25 risks being identified? Should the risk assessment include a vulnerability like “inadequate documentation of policy, process, and standards”? That would significantly increase the number of identified risks that need treatment, even if the treatment is simply creating the documentation around the controls.
Does there have to be a direct correlation between the risk assessment and all of the controls selected in the SOA?
If my email is confusing, perhaps we can have a conversation.
Answer: First you have to remember that to treat a risk you can use more than one control. In general, the controls are combined in this way:
- You establish policies, to define and formalize the rules and behaviors that are expected to be followed (e.g., information security policy, access control policy, backup policy, etc.)
- You establish procedural, physical, and technological controls to enforce the policies (e.g., incident management process, physical and logical perimeters, two-factor authentication for access control, etc.)
So, depending on the identified risks, you may have one or several controls associated to them, which may cover the 107 controls you are expecting. For example, for a risk of loss of data stored on servers due to a ransomware attack, you can consider the application of controls A.12.2.1 Controls against malware and A.12.3.1 Information backup.
Regarding the lack / inadequacy of documentation, you can consider it as a single systemic vulnerability (this way it will not increase much the number of risks to be treated) and consider for the risks related to it the application of controls A.5.1.1 Policies for information security and A.5.1.2 Review of the policies for information security.
Finally, the controls defined in the Risk Treatment, as well as those identified as implemented in the Risk assessment, must be identified as applicable in the SoA. Additionally, some controls can be marked in SoA as applicable even though they were not identified in risk treatment - in this case the reason for selection could be e.g. “good practice “.
Respuesta: Generalmente las compañías definen 4 niveles de confidencialidad: Confidencial (información más confidencial de todas), restringido (nivel medio), interno (el nivel más bajo), y público (lo puede ver cualquier persona, de dentro, o de fuera de la empresa). Por tanto, si todos los empleados (y sólo los empleados de la organización) pueden ver el documento, podrías establecer el nivel "Interno", o si sólo lo pueden ver algunos empleados (responsable de proyecto, responsables de área, etc), podrías establecer el nivel "Restringido", o si sólo pueden ver el documento roles específicos (por ejemplo, sólo la alta dirección), podrías establecer el nivel "Confidencial". Este artículo te puede resultar interesante “Information classification according to ISO 27001” : https://advisera.com/27001academy/blog/2014/05/12/information-classification-according-to-iso-27001/
Identification of applicable controls
Answer: ISO 27001 it does not have a set of basic controls, rather they have to be selected through a risk assessment process, and to identify the controls required for an organization you must verify its Statement of Applicability (SoA) and results of risk assessment. These documents will provide you information about how the organization perceives its risks and how they are going to treat them (since each organization is unique in its context and risk appetite, they will have different approaches considering the same risks, and you should take that into consideration).
This article will provide you further explanation about controls selection:
- The basic logic of ISO 27001: How does information security work? https://advisera.com/27001academy/knowledgebase/the-basic-l ogic-of-iso-27001-how-does-information-security-work/
Answer: I would say you have to identify first for what purpose this organization needs a certificate – if your clients prefer ISO 9001 better than ISO 13485, then you should go for the ISO 9001, and vice versa.
The right to be forgotten is not an absolute right that the data subject has in relation with its data. A controller does not need to comply with such a request the processing is:
- necessary for rights of freedom of expression or information;
- for compliance with a legal obligation under Union or Member State law;
- in the public interest or carried out by an official authority;
- for public interest in the area of public health;
- for archiving or research;
- for legal claims.
So, as you can see if there is a legal obligations set forth under Member State law then you need to keep the data even if the data subject requests for the data to be deleted.
As you can imagine there is no explicit requirement in ISO 9001:2015 to support those auditor demands. I do not know the particular requirements that your customers demand about the painting job, in the past I worked with a company that had to ensure a certain thickness layer of paint over a metal. Th e requirement was not on the paint characteristics but on the result, on the thickness. For that, they used an instrument to measure the thickness. If there is no customer requirement, and if in your risk assessment you saw no problems with the viscosity of the paint, there is no requirement to do what the auditor is asking.
The following material will provide you information about product release:
There is no mandatory requirement from ISO 9001:2015 to keep documented information about the context of an organization. That is up to each organization to decide if they will document it and how. For example, it can be a meeting minute where a SWOT matrix was created and analyzed. About legal requirements, your organization can keep a database of all the legal requirements applied to your own organization. Your organization should know the legal requirements to be able to assume the compromise of meeting them.
The following material will provide you information about the context of an organization:
Answer: According to ISO 27001, clause 10.1 b) 2), causes of nonconformities shall be determined in order to evaluate the need to take action to eliminate them and prevent nonconformities recurrence, or occurrence elsewhere. Considering that, since the outsourced services are affecting your ISMS, a root cause analysis must be performed.