Start a new topic and get direct answers from the Expert Advice Community.
CREATE NEW TOPIC +Guest
No, you do not need to create a totally new quality manual. The ISO 17025 Quality Manual serves to document the overall Lab Quality Management System, providing a way to reference and link all the requirements together in one place. Your laboratory can implement ISO 17025 according to Option B. You can use your already established ISO 9001:2015 quality management system (and manual) to demonstrate compliance with the requirements for ISO 17025 clauses 8.2 to 8.9. What is important is that processes must be implemented and maintained in a manner that supports and demonstrates the fulfilment of ISO 17025:2017 Clauses 4 to 7 for all your laboratory activities. This means that the way that the processes (8.2 to 8.9) were established, how they are performed, documented and controlled, must include the activities in Clauses 4 to 7. For example, your audit programme must be revised. You will start with a gap evaluation to determine what new processes you need to include, what mandatory documentation and records you need to “add-on” and include in your Quality Manual.
You can download a free Project Plan for ISO/IEC 17025 implementation from the ISO17025 Academy at https://info.advisera.com/17025academy/free-download/project-plan-for-iso-17025-implementation to assist you; as well as preview the ISO 17025 Quality Manual at https://advisera.com/17025academy/iso-17025-documentation-toolkit/
For more information on Option B, see the article Maintaining and improving quality management in laboratories according to ISO 17025:2017 at https://advisera.com/17025academy/blog/2019/08/30/iso-17025-maintenance-and-improvement-in-laboratories/For more information on the relationship between ISO 9001 and ISO 17025, see the article ISO 17025 vs. ISO 9001 – Main differences and similarities at https://advisera.com/17025academy/blog/2019/07/11/iso-17025-vs-iso-9001-main-differences-and-similarities/
First, it is important to note that ISO 27001 does not prescribe levels of security, only that the information is adequately protected.
In this context, what generally occurs is the definition of information classification levels (eg public, restricted, and confidential), which require an increasing order of resources as the classification of information increases. The specific resources to be used will depend on the outcome of the risk assessment and applicable legal requirements.
For more information, see:
As you mentioned initial, medium and advanced levels, I understand that it is also worth mentioning process maturity, which is also not required by the standard, but which can help in the implementation of the information security management system.
For more information, see:
The definition of scope depends primarily on the information you want to protect (e.g., customer information, R&D information, financial information, all information, etc.). Based on the information you want to protect you can identify locations, processes, or business units where this information is stored, processed, or flows through to include in your scope.
For example, if you want to protect customer information only, the processes related to cloud management services should be in the ISMS scope.
These articles will provide you a further explanation about scope definition:
These materials will also help you regarding scope definition:
Thanks very much Rhand!
Both certifications are good and complement each other for a person looking for a career in information security because they offer different perspectives about how information interacts with the business.
ISO 27001 lead auditor focus on auditing information security management. CISA goes beyond auditing the scope of information security, and also consider the audit of strategic relationships between information security and the information systems and business objectives.
This article will provide you a further explanation about CISA and ISO 27001:
This material will also help you regarding ISO 27001 Lead Auditor:
ISO 22301, ISO 27001, and ISO 9001 shares many common requirements:
These shared requirements allow an organization to save time and effort when integrating ISO management standards, because you will only have to make minimal adjustments to ensure compliance with common requirements, and you have more time to focus on the specifics of each standard.
Additionally, ISO 27001controls which requires the implementation of business continuity capabilities also can make use of ISO 22301 practices to fulfill these requirements. Of course, to implement ISO 9001 you may also require business continuity capabilities, and it also can benefit from ISO 22301 practices.
This article will provide you a further explanation about integrated systems:
This material will also help you regarding an example of integrating systems:
Primeiro é importante notar que a ISO 27001 não prescreve níveis de segurança, apenas que a informação seja adequadamente protegida.
Neste contexto, o que geralmente ocorre é a definição de níveis de classificação da informação (Ex.: pública, restrita e confidencial), os quais requerem uma ordem crescente de recursos a medida em que a classificação da informação cresce. Os recursos específicos a serem usados dependerão do resultado do levantamento de riscos e dos requisitos legais aplicáveis.
Para mais informações, veja:
Como você mencionou níveis inicial, médio e avançado, entendo que também vale mencionar maturidade de processos, que também não é requerido pela norma, mas que pode ajudar na implementação do sistema de gestão da segurança da informação.
Para mais informações, veja:
According to ISO 22301, a Business Continuity Plan must contain:
To see how a BCP compliant with ISO 22301 looks like, please access the free demo in this link: https://advisera.com/27001academy/documentation/business-continuity-plan/
This article will provide you a further explanation about BCP content:
This material will also help you regarding BCP content:
This means that, when you detect a nonconformity, first you need to eliminate it, then you need to plan how you will eliminate the cause of this nonconformity. So you need to find out what is the cause of that nonconformity and find out with what actions this cause will be eliminated. When you know your actions, then you need to plan them and document them. If the action requires a change in your documentation, then you should also need to make a change in the proper documentation. Usually, there is a form that covers all elements for properly solving the nonconformity.
Here is the link to the preview of the request form from our ISO 13485:2016 Documentation toolkit:
For more information on how to solve corrective action, please see the following articles:
In our ISO 13485:2016 Documentation toolkit, you can also see Procedure for corrective action:
Put a sheet of scenery paper affixed to a wall. Then, bring together a diverse team of people who as a whole know the company from different perspectives. On one end of the paper put a sticky note saying, "Customer in need" and on the other end put another sticky note saying "Customer served". Then, in a collaborative brainstorming session use sticky notes to describe what happens from "Customer in need" until "Customer served". Follow a rule: each sticky note has a verb + a noun. For example: Receive order; Check order; Confirm order; ...
When you feel you have already listed the essential activities, try to group them into what will be the organization's processes.
This technique is described in this free webinar on demand - The Process Approach - What it is, why it is important, and how to do it - https://advisera.com/9001academy/webinar/iso-9001-process-approach-free-webinar-on-demand/
In my example we get this global process map:
Then, for each process, based on the individual sticky notes you can draw a flowchart:
Then, for each process, you can apply the risk-based approach and determine steps that need to be improved, either by changing practices, either by introducing SOPs, or either by introducing new controls.
Please find an example from the above webinar here:
The following material will provide you more information about the process approach: