Answer
After certification your organization will have surveillance audits.
Surveillance audits exist to check if your management system is working as designed. So, pay special attention to records. Are all the incidents being recorded? Measurements, complaints, corrective actions, non-conformities, internal audits, and management review, etc. Remember, if your organization had any minor non-conformity or observations during the certification audit, be sure that auditors will look into those issues with special care.
The context change, priorities change, objectives change. So, be aware of the need to update management system documentation. For example, a new product line, a new machine, a new market, can lead to changes in processes and procedures.
The short answer would be no, you do not have to complete it.
However, when a work procedure instruction is being developed it is a good practice to include safety, environment, and other topics. When people work, they don’t just do productivity work, or quality work, or safety work, or environmental work, they just work, period. And while working they do it with all those topics in mind. The work is a whole, not a sum of parts. About the risk assessment, ISO 9001:2015 does not require any records. I think that a good work procedure instruction can be a good answer to a previous risk assessment. In a work procedure instruction, one can list “what is there to do to reach a set of desired outcomes”. Risks are what can prevent us from achieving these expected results. Thus, in addition to including what to do, work procedure instruction can also include actions and concerns to minimize or avoid the most relevant risks.
The following material will provide you more information about risks:
Considering your stated background, in fact the ISO 27001 Lead Auditor course is the best option for start your civilian career.
Our exam for the ISO 27001 Lead Auditor course is certified by Exemplar Global, and is globally recognized and accepted as evidence of competence to audit ISO 27001 Information Security Management systems.
Developing key performance indicators for a division in an organization
Answer
First of all, I would like to set a common language to avoid misunderstandings from both parties. The following figure shows my interpretation of “division”:
Corporation is what you call organization.
A division is the head or the umbrella of a set of business units.
Normally, a division does not sell to customers. Sales to customers are done through each business unit.
Business units have their own strategies to drive customer derived value.
A division have a division strategy to drive value from the alignment and synergy of different business units, belonging to the same division.
So, to develop relevant key performance indicators for a division, one must first identify how the division intends to generate value from the fact that different business units belong and can work together. For example, they can share customers, and, in that way, they want to promote cross-sel ling; they can share processes and services; they can share intangible assets; they can share a common brand; they can share capital. Key performance indicators for a division should be indicators that highlight, promote and monitor both the behaviors and the outcomes of those sharing drivers.
Risk Assessment and Risk Treatment Methodology-Cloud
Please see response from Advisera: "Risk Assessment and Risk Treatment Methodology Cloud covers not only requirements for ISO 27001, but also specific requirements applicable for cloud environments defined by ISO 27017 and for Personal Identifiable Information PII) defined by ISO 27018."
Answer:
First of all, thanks for this feedback.
Please note that ISO 27017, in its clause 4.4 (Managing information security risks in cloud services) does not define any additional requirements for the risk management process, only that it is advised to refer to requirements for risk management defined fo r ISO 27001, and considered in its application cloud environment specifics (e.g., risk sources, threats and vulnerabilities), and these specifics are already included in risk assessment and risk treatment tables.
Considering that, we will be adding this reference to ISO 27017 to this Risk Assessment and Risk Treatment Methodology Cloud template to avoid misunderstandings, but there is no need to make any other change in the document, and the document you have is fully compliant with ISO 27017.
Business objectives for BCMS
Answer:
Examples of business continuity objectives may be:
- Comply with xyz law/regulation by December 31, 2020, using ISO 22301 methodology
- Enter a new market in the next 12 months because of the ISO 22301 certificate
- During 2020, improve our recovery time by 12 hours while not incurring new costs.
Certification audits normally consider two degrees for non-conformity severity (and both are considered serious):
- Minor non-conformity: a nonconformity that does not affect the capability of the management system to achieve the intended results.
- Major non-conformity: a nonconformity that affects the capability of the management system to achieve the intended results. For example, if the company completely failed to fulfill a certain requirement; if a process has completely fallen apart; or if you have several minor nonconformities that are related to the same process or to the same element of your management system.
Regarding the certification / re-certification process, minor non-conformities identified during the process does not affect the certificate (provided that you present an action plan for the auditor). On the other hand, a major non-conformity is an impediment for the certification, until the situation is solved.
Pleas e note that the definition of major and minor non-conformity are based on best practice used by certification bodies and certification auditors. ISO 17021, the ISO standard for bodies providing audit and certification of management systems, states that a non-conformity shall be classified (but it does not define the classification to use). Also note that this grading is not mandatory for internal audits (most often such grading is not necessary for internal audits).
Even though you do not have access to data processed by the customer, you still have access to some kind of data from your customer, like email addresses for support contact, personal data of the person responsible for the contract/ service agreement, financial data for billing process, etc.
So, you have to consider this kind of data on your your Policy for Data Privacy.
The main tip here is the question: which information the customer has to send me so I can setup his service and billed him?
If you have any specific doubts in mind please contact us, so you can help you with them.
Handling risk
Answer
Organizations determine risks and then evaluate them. ISO 31000:2018 presents several options to handle relevant risks:
* Avoid risk by deciding not to start, or not to continue, with an action that raises it;
* Accept or increase the risk in order to pursue an opportunity;
* Remove the source of the risk;
* Lower the probability;
* Change the consequences;
* Share the risk with another party or parties;
* Maintain risk based on informed decision;
* Take advantage of opportunities.
Your “preventive” interpretation is applicable when avoiding risk and when lowering the probability, for example.
The “correct and fix” interpretation is less common but applicable when removing the s ource of risk. So, both, in certain way are correct. Although the “preventive” approach is much more common.
Answer:
The root of both of your questions is the difference between processes and procedures, so it is best to answer them together. A process is anything that you do that takes inputs, does something to them, and creates outputs (this does not mean that the activities need to be in a specific order). A process does not need to be documented. A procedure is a set way of doing a process, so when the activities need to be done in a certain order (this does not mean that the procedure needs to be written down). A documented procedure is when you choose to write a procedure down. If will give you an example using a purchasing process; I like using purchasing because it is easy to understand.
So, as an example: If you have a process that states that your purchasers will get a purchase request, choose some vendors from the approved vendor list, find prices online, and then place an order of the best value; you have a process (i n this case you may then find prices online first and then look at the vendor list to make sure the vendors are approved because the order doesn’t matter).
If you decide that the order matters and you want to do the steps in the order listed (purchase request, approved vendor list, find prices, place order) then this becomes a procedure. Note that if you only have a few purchasers, and don’t think you need to write this down because it is not complex, you now have a procedure that is not documented, but it is still a procedure.
By writing down the procedure you have a documented procedure. You can do this an any way that works for you; flow chart, text document, etc. The important thing to remember is that if by not writing down the procedure you could have a process nonconformity, you should write down the procedure.
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.