Answer: I'm assuming that by "measure"you are referring to "security measure". Considering that, a "measure" is a control to treat the risk, while a "guideline" is an orientation about how to implement that control. For example, backup is a measure to treat the risk "loss of data due to hardware failure", while a guideline is the orientation that backup media should be regularly tested to ensure it is ready to use if required.
ISO 27001 provides security measures in the form of security controls listed in the Annex A, while implementation guidelines are provided in the ISO 27002 standard.
In case of process effectiveness and efficiency, the requirements of IATF 16949 are too vague to discard this requirement of the Lead Auditor, although the standard itself doesn't say that every single process needs to be measured for efficiency and effectiveness. Unfortunately, I think you will have to measure effectiveness and efficiency of all processes, but during the management review, you can decide to stop it for some or most of the processes (topically supporting processes).
When defining and documenting processes you need to apply requirements from clause 4.4,1 for every process. To distinguish between process and procedure, the easiest way is the process is set of activities that result in certain outcome and the procedure is description on how the process is carried out. For more information, see: ISO 9001:2015 process vs. procedure – Some practical examples https://advisera.com/9001academy/blog/2016/01/19/iso-90012015-process-vs-procedure-some-practical-examples/
Exclusions
Answer:
Any exclusion must be explained and providing only services is not an acceptable justification for excluding clause 7.3 in ISO 9001:2008. If your company has a set of services that provides to customers and there is no intention of developing new services then clause 7.3 in ISO 9001:2008 or clause 8.3 in ISO 9001:2015 can be excluded. The management system scope decision can be very important to influence exclusion justification. A company can develop new services but exclude them from the scope by being very precise about what includes within the scope.
The following material will provide you information about exclusion:
Answer: ISO 2700 cannot be implemented to products. It is a management system standard aimed to protect information related to organization's processes, business units or locations. Regarding the organization, ISO 27001 can be implemented to specific processes, business units or locations or you can define the entire organization as the ISO 27001 scope.
2 - To start with risk assessment ISO 27001, is it mandatory to have process list identified first followed by identification of assets and then final risk assessment.
Answer: ISO 27001 does not prescribe any specific methodology for risk assessment, so orga nizations are free to choose the approach that suits them best.. That said, it is not mandatory by the standard to have a process list identified first.
In this white paper you will find information such:
- The types of costs faced within an ISO 27001 implementation project
- How different implementation options could affect your budget planning
- Tips to improve budget planning
- How to verify your budget outline
I also would like to remember you that included in the toolkits you bought you also have access to expert support to help you with the templates, answer questions and evaluate documents, so you can include this approach among other consultancy alternatives you may be considering.
Unfortu nately we have no such materials for SOC 2, but many concepts and examples in the white paper can be extrapolated to SOC 2.
Customer visit and customer satisfaction
Answer:
In reality it doesn’t matter, it is just a box, consider that it belongs to customer satisfaction, or customer communication, or even a tool to win customers, or interested parties’ relationship development. What matters is that your organization believes that customer visits is something worth investing to do it professionally
The way of maintaining the knowledge depends on the way how the knowledge is stored. The purpose of this clause is to ensure the knowledge is up to date. So, in order to maintain the knowledge, you need to identify it first, and it can be in form of work instructions, procedures, etc, and then you need to define how you should keep it up to date and available to the relevant people.
Answer: If you have the Data Protection Officer, then this is the person responsible for data protection in your company.
If you do not have such function, you can assign a role of person responsible for data protection to someone like Head of IT department, Head of legal department, or similar - GDPR itself does not provide any guidelines on this, but it would be good to have someone with enough authority in the company to make important changes.
The requirements for product safety cannot be excluded even if there are no safety issues related to the product. If you are not designing the product and get the drawing from the third party (e.g. customer), they should provide you with information on the product safety. If they don't, you should conduct risk assessment to determine if there are any risks related to the product safety and take appropriate actions. Even if there are no product safety issues, you will still need to have the product safety process.
Thanks for taking time from your busy schedule to reply to me.
Answer: ISO 27001 does not prescribe any solution to be applied for security controls in Annex A, only objectives to be achieved. This gives organizations freedom to implement the most adequate solutions according to their context. For guidelines and recommendations about what to consider in the implementation of security controls, you should consider the ISO 27002 standard.
That said, regarding security of system passwords, service passwords, and application passwords, including passwords at administrator level, you should consider ISO 27002 recommendations for the following controls:
- Control A.9.2.3 (Management of privileged access rights): for shared administration user IDs, you should consider practices like changing passwords frequently and as soon as possible when a privileged one user of these shared IDs leaves or changes job, and communicating these passwords to administrators through secure mechanisms. Besides that, all other recommendations from control A.9.3.1 (Use of secret authentication information), aimed for general users, should also be applicable to administrators.
- Control A.9.3.1 (Use of secret authentication information): when passwords need to be part of automated log on procedures they must be properly protected (e.g., do not store password on plain text)
- Control 9.4.3 (Password management system): when stored, password should be kept on files separated from application system data.