Search results

Home / Search

Category:
Select
Select

11275 results

Guest

Guest

Create New Topic As guest or Sign in

HTML tags are not allowed

Select

Assign topic to the user

  • Asset Owner

    First is important to note that ISO 27002 is not mandatory to implement ISO 27001, it only provides guidance to support the implementation of controls from ISO 27001 Annex A.

    Considering that, the main role of an asset owner is to ensure his asset is properly protected, and in some cases, he will not perform security activities by himself but needs to ensure these activities are performed.

    In the case of the laptop, by "User" we mean the "Person who is using the laptop", and if an auditor questions your choice of this role as the asset owner, you need to show evidence to the auditor about who performs the security activities he asks for and how the laptop user ensures it is performed.

    For example, to ensure information availability, the person using the laptop may require backup copies to be created, and needs to ensure backups are being performed and to do that this person may require testing the backup media by asking for the restoration of specific files.

    For further information, see:

  • Key Risk Management Plan template

    I’m assuming that by “Security Risk Management Plan” you mean for planning how to implement risk treatment.

    Considering that, in your toolkit, there is a Risk Treatment Plan template where you can define what needs to be done to implement risk treatment. You can find this template in folder 07 Implementation Plan.

    For further information, see:

  • Risk based calculation

    ISO 27001 does not prescribe how to calculate risks, so organizations can adopt the approach that better suits their needs. 

    Considering that, please note that the most commonly used approach is the asset-threat-vulnerability, which does not use only physical assets, but also, information, data, services, and other kinds of assets, where risks are determined according to their impacts related to information Confidentiality, Integrity, and Availability.

    For further information, see:

    In this article you will find information about:

    • Main steps in risk management
    • Risk assessment methodology
    • Risk assessment
    • What to use instead of an asset-based approach for ISO 27001 risk identification

    • Inquiry

      ISO 27001 does not prescribe controls hierarchy to be implemented, so large majority of companies do not differentiate between high and low level controls. We also do not recommend this approach because it only creates an overhead.

      Although ISO 27001 does not specify this, you could apply "high-level" and "low-level" concept to policies - the top-level Information Security Policy could be considered as a "high-level" policy because it defines security rules for a whole company, whereas a "low-level" policy could be Backup policy because it defines security rules for only one part of the company.

    • ISO 27001 EA Codes

      I’m assuming that by EA Codes you mean the codes for ISO Certification Scope.

      Considering that, EA Codes are not used or required by ISO 27001. They are used by certification bodies during the certification process to identify the main business activity related to the certification scope.

    • Implementing ITSM and Agile Methods Together

      Thanks for that information 

    • Risks to Impartiality

      Yes, you are correct in your interpretation. A laboratory needs to consider possible risks to impartiality (in terms of the definition of impartiality), then identify any that may be possible  (even if low probability) in your context (what you do, who your clients and external providers are, and what your organizational structure is). They are many aspects that are covered under impartiality. These are explained in the definition of impartiality in ISO 17025, where impartiality is simply the

      presence of objectivity; meaning there are no conflicts of interest (or they are resolved/safeguarded)are resolved so that there are no factors that can negatively influence activities of the laboratory. Look at the standard for the other terms such as “freedom from bias”. So anything that will impact any established policies including a Code of Conduct. For example, personnel is put under undue pressure where they have to as you say take shortcuts that may jeopardize the results. Everything must be in place to ensure competent, consistent operations. i.e. consistently valid results.

      You asked
      is there a good way to communicate these?

      Through risk analysis and the use of tools showing cause and effect, and fishbone diagrams. Involve all relevant personnel. Use brainstorming and set out a process chart for an activity showing the inputs and outputs and the influencing factors. Then indicate the controls in place. Using your risk register indicate whether with those current controls (risk treatment) if the risk is at an acceptable level or not. Then record how you will monitor the effectiveness over time – for example, monthly meeting discussions, when onboarding new personnel, clients, or suppliers, and during internal audits,

      For more information, have a look at the advice answers

      Compliance with the ISO/IEC 17025:2017 requirement for Impartiality - https://community.advisera.com/topic/compliance-with-the-isoiec-170252017-requirement-for-impartiality/

      Procedure for impartiality - https://community.advisera.com/topic/procedure-for-impartiality/

      The ISO 17025 document template: Registry of Key Risks and Opportunities, is available for as part of the toolkit for preview and purchase separately too at  https://advisera.com/17025academy/documentation/registry-of-key-risks-and-opportunities/

    • Disaster Recovery and Business Continuity Testing

      Considering the most used standards for these topics (ISO 27001 for information security and ISO 22301 for business continuity), these standards do not prescribe how often testing and exercises should be taken.

      To comply with these standards, you need to perform a risk assessment and identify applicable legal requirements to define the proper frequency for these testing and exercises.

      In case your risk assessment and requirements do not provide a proper reference, you can try starting with these suggestions:

      • testing backups and sequel databases - e.g., once a quarter
      • BC testing and exercises - e.g., once a year

      For further information, see:

Page 43-vs-13485 of 1128 pages

Didn’t find an answer?

Start a new topic and get direct answers from the Expert Advice Community.

CREATE NEW TOPIC +