1. To establish and implement a quality management system.
2. To allocate appropriate resources, responsibility and authority across the company organization.
3. To achieve ZERO complaints from our customers.
4. To deliver ZERO defective products to our customers.
5. To have proper control over the cost of (poor) quality.
6. To deliver our products on-time as per the agreed schedule with our customers.
7. To constantly build competencies to raise our organization’s performance
Since we need to have a SMART objective, can you advise how I can interpret it to show that we have achieved the objective.
Answer:
As you mentioned objectives should be designed to be S.M.A.R.T (specific, measurable, achievable, realistic and time-based), so it is important that you first review them in order to make then trully S.M.A.R.T. For instance:
- S - Specific - The objective should be focused on only just one thing. For instance, "To have proper control over the cost of (poor) qua lity" is not specific, you should specify for example which processes need to be controlled or what costs.
- M - Measurable - It should be possible to measure whether or not you achieve the objective. For instance, "deliver our products on-time" is too general, you should specify how much you will improve that delivering, for instance up to 99% in 48 hours delivering.
- A - Achievable - The objective should be within your capabilities, i.e. is it really achievable that ZERO stated in two of the objectives, maybe you can establish a decreasing %, from 5% to 2%.
- R - Relevant - The objective should be something of importance. I think your objectives already meet this condition.
- T - Timed - There should be a timescale or deadline for achievement of the objective. An objective needs to have a time associated with it, for example within the next year.
Setting this way the objectives you will be able to evaluate if you already have met it or not.
As it is stated in our procedure of Addressing Risks and Opportunities you need to evaluate the actions taken for addressing risks and opportunities. You can monitor and measure the actions analysing and evaluating the data gathered in order to determine their effectiveness. Your organization can use different methods to do that, such as Key Performance indicators, business metrics, internal audits, monitoring of corrective actions and action plans and subsequent reporting into management reviews.
The publication of documentation has the purpose to make people who need them aware and able to access it when needed. So, to fulfill requirement 7.5.3 (Control of documented information) every time a policy or procedure is revised/modified, or when a new one is created, it has to be published according defined practices
Physical security and human resources policies templates
Answer:
Included in your toolkit there is a List of Documents file that correlates each template with clauses and controls of ISO 27001.
Related to physical security and human resources policies the toolkit has the following templates:
- Acceptable Use Policy, located on folder 08 Annex A ==A.8 Asset management
- Clear Desk and Clear Screen Policy, located on folder 08 Annex A ==A.11 Physical and environmental security
- Disposal and Destruction Policy, located on folder 08 Annex A ==A.11 Physical and environmental security
- Procedures for Working in Secure Areas, located on folder 08 Annex A ==A.11 Physical and environmental security
- Supplier Security Policy, located on folder 08 Annex A ==A.15 Supplier relationships
These templates cover requirements for sections A7 (Human Resource Security) or A.11 (Physical and environmental security), depending on the template purpose.
ISO and COBIT
1- If my company require to follow both standard ISO and COBIT, so what will be affect to the IT Risk Management Process? which standard should I follow for implement IT Risk Management?
Answer: ISO and COBIT requirements for risk management are very similar (identify, analyse, evaluate and treat the risks), the difference being that for ISO 27001 you have to consider effects of risks on information (in terms of confidentiality, integrity, and availability), while for COBIT you have to consider risks for IT assets (e.g., hardware and software) not related only to information (e.g., risks related to operational performance or cost efficiency). Considering that, if you follow both standards, your IT Risk Management Process will have to include evaluation criteria related to information security and assess and treat risks also considering how the affected IT assets will impact information.
Regarding implementation, ISO 27001 only requires the definition of a methodolog y, while COBIT also provides details about risk management, so you can use COBIT approach.
2 - I got many assets and applications in my company, I want to do IT risk management on some asset and application by following ISO 27001:2013 and the remain asset and application I will do the IT Risk management later, I wonder that if I do like this the SOA is remain the same or different?
Answer: The SoA covers the controls applicable to treat risks related to information security, so if the IT risk assessment you perform later does not identify additional risks (please review the previous answer) that can affect information, then the SoA will not change. On the other hand, if a risk affecting an IT asset will also impact information and this one is considered unacceptable and you have to implement a new control, listed or not on ISO 27001 Annex A (e.g., a control required by COBIT), then this situation will require you to change your SoA (you can included on SoA controls not listed on ISO 27001 Annex A if these controls will treat information security related risks).
3 - Could you please explain and give an example related to Quantitative and Qualitative term of risk assessment?
Answer: In qualitative risk assessment, the focus is on interested parties’ perceptions about the probability of a risk occurring and its impact on relevant organizational aspects (e.g., financial, reputational, etc.). This perception is represented in scales such as “low – medium – high” or “1 – 2 – 3,” which are used to define risk’s final value.
In quantitative risk assessment, the focus is on factual and measurable data, with highly mathematical and computational bases, to calculate probability and impact values, normally expressing risk values in monetary terms.
Neither ISO 27001 nor EU GDPR require the documentation of an IT Strategy, so there is no such template included in the toolkit, so organizations are not overwhelmed by non required documents.
Answer:
Giving generic root causes and corrective actions is difficult because when the corrective action process is done well it needs to be very specific for the systematic problem that was faced. For instance, if you were investigating an error in the design of a part you may find that there was a root cause problem with the calculations cause by an input error in the program and the corrective action would be to correct the drawing and put in a better check system for the inputs. However, if you found that the root cause was due to a previously unidentified problem in the calculation system you may need to take action to put in place the temporary check procedures and systems corrections and updates necessary to address this risk which could entail a very lengthy implementation plan.
IT General Controls are controls that are common to IT processes, providing stable and effective operation of application controls. They cover fields like creation / acquisition of systems, SDLC Process, access control, back up, change control, etc. ISO 27001 is one way to implement ITGC, providing objectives and, through ISO 27002, detailed implementation guidance.
2.What is the difference between external and internal auditors and practically how internal auditor assists external auditor ?
Answer:
The internal auditor performs audits on behalf of the organization that owns the management system, while the external auditor performs audits on behalf of an organization's client (second-party auditor) or a certification body (third-party auditor). Norm ally the internal auditor may act as the guide for the external auditor, providing some general orientation for the performing of the external audit.
Do you think it is possible to exclude A.12.1.2 for this area from our applicable controls without loosing the certification status?
Answer:
If I understood correctly, the only issue in your current change process is about raising the change in advance. Considering that, the standard requires to control the changes, not necessarily to "raise" them in advance, so there is no need to exclude all the control (you can only exclude the "raise" in advance part).
To exclude a control you have to demonstrate that this exclusion won't arise unacceptable risks, neither will mean not fulfilling contracts, laws or other legal requirements that your organization must be compliant with.
If you can satisfy these conditions this exclusion will not affect the ISO 27 001 certification (but it does not seem your case).