Search results

Lead Auditor certification

Please note that accreditation only applies to organizations that certify other organizations' management systems (e.g., ISO 27001, ISO 9001, etc.), or certifies people that are approved on their training (e.g., Lead Auditor, internal auditor, etc.).

Considering that, once you have passed the Lead Auditor exam from an accredited training provider there is no need to submit your certification for accreditation. The fact that the provider is accredited already validates your certification.

For further information, see:

• Accreditation vs. certification vs. registration in the ISO world https://advisera.com/articles/accreditation-vs-certification-vs-registration-in-the-iso-world/
• Accredited ISO certification versus non-accredited: What it means and why it matters https://advisera.com/articles/accredited-iso-certification-versus-non-accredited-what-it-means-and-why-it-matters/

Documentation hierarchy

ISO 27001 does not prescribe documentation hierarchy, so organizations can adopt the framework that best suits their needs.

Considering that, using ISO 10013 as a reference for documentation hierarchy is an acceptable approach.

Regarding the fact that ISO 10013:2001 is a withdrawn standard, unless you have specific requirements to adopt this version (e.g., customer requirement or law), you should consider using the 2021 version of the standard, because its requirements are better aligned with current versions of ISO management systems standards.

For further information, see:

• How to structure quality management system documentation https://advisera.com/9001academy/knowledgebase/how-to-structure-quality-management-system-documentation/

• Does a company need to be ISO certified to present a Quality Manual?

  No, any company can prepare a quality manual. By the way, ISO 9001:2015 no longer mentions a quality manual.

  Please check these articles:

  • The future of the Quality Manual in ISO 9001:2015 - https://advisera.com/9001academy/knowledgebase/the-future-of-the-quality-manual-in-iso-90012015/
  • How to write a short, concise Quality Manual - https://advisera.com/9001academy/knowledgebase/writing-a-short-quality-manual/

• Information Security Policy Creation

  Examples of Information Security Objectives are:
  - decrease the impact and/or number of information security incidents by 30% in 12 months
  - increase revenue of service XYZ by 5% in 12 months
  - win a new customer in 6 months
  - increase market share by 3% in 12 months

  For further information, see:

  • ISO 27001 control objectives – Why are they important? https://advisera.com/27001academy/blog/2012/04/10/iso-27001-control-objectives-why-are-they-important/

• Statement for logs retention periods regarding critical assets

  ISO 27001 does not prescribe retention periods for logs.

  To define proper retention periods, you need to perform a risk assessment and identify applicable legal requirements.

  In case your risk assessment and requirements do not provide a proper reference, you can try starting with a retention time of one year.

  For further information, see:

  • Logging and monitoring according to ISO 27001 A.12.4 https://advisera.com/27001academy/logging-according-to-iso-27001/

• Distributor vs Supplier quality agreement

  Quality agreement should be with the actual manufacturer because you need to be sure that the device is produced in accordance with ISO 13485 and MDR.  

• ISM Policy

  ISO 27001 does not prescribe which objectives to define, so you can use objectives related to your business strategy, to specific customers and regulators you must comply with. Additionally, you can also use more specific objectives related to security controls, security processes, etc.

  Some specific examples are:

  • win a new customer in 6 months
  • increase market share by 3% in 12 months

  For further information, see:

  • ISO 27001 control objectives – Why are they important? https://advisera.com/27001academy/blog/2012/04/10/iso-27001-control-objectives-why-are-they-important/

  • Custom Control Creation

    Considering your stated situation (Having operating system software and databases that are at the end-of-support life cycle), suggested assets, vulnerabilities, and threats, with respective controls are:

    • Assets: “Operating systems” and “Database management systems”
    • Vulnerabilities: “Rules for software and its databases not clearly defined” and “Requirements for software development not clearly defined”
    • Threats: “Maintenance errors” and “Application error”
    • Controls: “A.8.25 - Secure development life cycle” and “A.8.8  Management of technical vulnerabilities”

    Please note that end-of-support is part of the retirement step of an asset life cycle management process (in this case, applied to assets operating system software and databases), and so it is an expected situation for IT operations.

    Considering that, the vulnerability, in this case, would be related to not knowing what to do by this time.