Answer: For current suppliers you should consult the service agreement/contract established with each supplier. For new suppliers, to have an access to their SoA, should be condition of the suppliers selection process, because this document can provide you a general overview of how the supplier handles its own information security. But you should also note that suppliers can refuse to present their SoAs, and you should be prepared to consider that too in your selection process (maybe include visits to potential supplier's premises for evaluation).
Hello
Thank you alot for this precious enlightenment.
Or can I take a course close to my location?
I work at Algeria Telecom Mobile Mobilis as infrastructure NGBSS system administrator OS and DBA expert level 3 .
In algiers .ALgeria
Best Regards.
Answer: ISO 27001 standard describes how to manage information security in an organization, while COBIT provides implementable controls over information technology, organized into IT-related processes. ISO 27001 provides many security control objectives applicable to information technology that can be used to enhance effectiveness of COBIT (e.g., controls from section A.13.1 Network security management) processes. Additionally, COBIT governance practices and ISO 27001 context understanding requirements can be used together to better align information security and information technology with business objectives.
This article will provide you further explanation about COBIT and ISO 27001:
- How to integrate COSO, COBIT, and ISO 27001 frameworks
Answer: First of all, the expression "there is no risk" is kind of incorrect (there is no situation risk-free). A more appropriate expression would be "all current risks are acceptable."
That said, to state 'sufficiency of controls' a company should identify which controls are applied to each identified risk and how these controls are being measured and evaluated to ensure they are sufficient. Based on that information an auditor can look for evidences of compliance. As for the identification of the most important control to ensure sufficiency, besides the identified risk you should consider the security requirements and objectives established to built a checklist of what to look for. Seasoned auditors can rely on their experience t o quickly identify them.
Answer: Although ISO 27001 does not prescribe any methodology for risk management, its requirements for risk assessment and treatment can be fulfilled by NIST's RMF (it is not a question whether they are similar or not, but that RMF is a framework that fits ISO 27001 very nice).
Auditing documentation requirements for ISO 9001 and ISO 13485
Answer:
If your Quality Management System is compliant with both ISO 9001 and ISO 13485, during the internal audit you need to check compliance with both standards. When it comes to common requirements or requirements related to the same elements of the system, you need to audit against requirements of both standards. Whichever standard has stricter requirements, those requirements should be applied and auditing should be done against those requirements.
Another option is to conduct separate audits for ISO 9001 and ISo 13485 but this would just mean that you will double the work.
Answer: For the purposes of a simple risk assessment, there is no difference if you add or multiply likelihood and consequence to calculate the risk. The difference would only make sense for statistical calculations, which are not required for simple risk assessment.
The standard requires organization to ensure confidentiality of the customer-contracted products and projects under development, including related product information. The standard does not specify what kind of protection of the information should be applied and in most cases it is either defined by the customer or usual confidentiality rules of the company are applied.
As far as documenting the requirement in the manual goes, you should explain what rules for confidentiality your company applies and who is responsible to enforce those rules.