Search results

Guest

Guest

Create New Topic As guest or Sign in

HTML tags are not allowed

Assign topic to the user

  • Group assets


    A couple of questions that the Attendees asked which was relevant in my situation because each company's scope is different and these were the following:
    1Grouping hardware together such as Router or Switches instead of individually  to make the impact and likelihood easier( Please correct if I'm wrong). On the contrary it might change because a Edge Router will have a different responsibility than a Access switch or an Distribution switch. Am I correct to say that it depends how I perceive these Assets and what impact it will have?
    2The type of methodology to use etc. low, medium and high OR 1-5.1-10............Regarding to this question, I find it easier to use the numbering because the Risk can be calculated easier and Management attendance can be attracted more easily( Once again please correct me on this point).
    The Treatment itself, is it advisable to implement a audit process for example quarterly to check on the progress of these devices that needs to be treated. What is your advice?
     

    Answer:

    A1: You are right. It is a b est practice to group assets, because for example you can have an asset “Routers” instead of a number of independent routers (all equals and with the same configuration). This approach will help you to reduce the number of assets in your inventory. You can group assets depending if they share threats/vulnerabilities and the risks are the same (based on impact and likelihood). So, from this point of view, if you have an Access switch that is different that a Distribution switch, you need 2 different assets in your inventory. This article about the asset inventory can be interesting for you “How to handle Asset register (Asset inventory) according to ISO 27001” : https://advisera.com/27001academy/knowledgebase/how-to-handle-asset-register-asset-inventory-according-to-iso-27001/
    A2: From my point of view, both approaches are ok for the standard, for some people is more easy to use numbers, and for other people is more easy to use names, but keep in mind that the important here is the methodology that you use to calculate the risk, which must be the same for the calculation of all risks, and you need to develop it in the easier way for your business. Do you know our Risk Assessment and Risk Treatment Methodology? It is also very easy, and you can see a free version clicking on “Free Demo” tab here “Risk Assessment and Risk Treatment Methodology” : https://advisera.com/27001academy/documentation/Risk-Assessment-and-Risk-Treatment-Methodology/
    Regarding your last question, you can perform tasks of reviewing periodically, depending of the deadline for the execution of the actions. For example, if the deadline for the implementation of a backup policy is 3 months, you can perform tasks of review each month. An audit process is more complex (if we talk about the internal audit), so you do not need to perform it to review the risk treatment, reviewing the actions planned and performed (Risk Treatment Plan) can be enough. 
    Finally, this article about the Risk Treatment Plan can be interesting for you “Risk Treatment Plan and Risk treatment process – What’s the difference?” : https://advisera.com/27001academy/iso-27001-risk-assessment-treatment-management/#treatment
  • ISO 27001 - ¿Por dónde empezar?


    La xxx de la xxx esta interesada en prepararse para obtener la certific ISO 27001, pero no sabes cuales son las acciones que debemos tomar para conseguirlo. ¨Por donde debemos comenzar?
     

    Respuesta:

    Antes de obtener la certificación tienes que implementar la ISO 27001:2013 in tu organización, y una de las acciones más importantes que necesitas llevar a cabo al principio es establecer un plan de proyecto. Por tanto, este artículo puede resultarte interesante  “Proyecto ISO 27001 - Cómo hacer que funcione” : https://advisera.com/27001academy/es/blog/2015/05/03/proyecto-iso-27001-como-hacer-que-funcione/
    Para empezar la implementación, también es importante obtener el apoyo de la Dirección, y ellos necesitan conocer cuales son los beneficios de la ISO 27001, por tanto este artículo también te puede resultar interesante “Cuatro beneficios clave de la implementación de la norma ISO 27001” : https://advisera.com/27001academy/es/blog/2010/07/21/cuatro-beneficios-clave-de-la-implementacion-de-la-norma-iso-27001/
    Por último, este artículo te muestra una sencilla lista de chequeo para la implementación de la ISO 27001, espero que pueda servirte de ayuda “Lista de apoyo para implementación de ISO 27001” : https://advisera.com/27001academy/es/blog/2010/09/28/lista-de-apoyo-para-implementacion-de-iso-27001/iso-27001/
  • Security controls to mitigate cybersecurity threats

    We have received this question: Which control clause(s) in ISO27001:2013 correspond to each of the following areas to mitigate cyber security threats: 1. Home, mobile working : Info. security regardless of how/where employees access company's info. assets 2. User Education and Awareness: All interested parties should be aware of key risk and how to report incidents. 3. Incident Management: Ability of the company to contain incidents and return to business as usual quickly. 4. Info. risk Management Regime: Tone from the top 5. Managing User Privileges: Role based security on a need to know/need to have basis 6. Removable Media Controls: Safe use and disposal of media 7. Monitoring: Preventive, reactive and corrective measures to curb unexpected activity 8. Secure configuration: Configuration and change management to maintain integrity and availability 9. Malware Protection: Effective Patch management to reduce exploitation of known vulnerabilities 10. Network Security: Knowing and controlling who accesses to the network Answer: First let me say you that I SO 27001 is not for a specific sector, for example cybersecurity, so ISO 27001 is a global standard that you can use to establish an Information Security Management System to protect information in any type of environment (including cybersecurity, but it is not only for this). Anyway, I will show you the clauses of ISO 27001:2013 that are more related to each point: 1.- A.6.2.1 Mobile device policy and A.6.2.2 Teleworking 2.- Clause 7.3 Awareness and A.7.2.2 Information security awareness, education and training 3.- Entire domain A.16 Information security incident management 4.- I suppose that you mean Risk management, if so, the clauses related to this in ISO 27001: 2013 are 6.1.2 Information security risk assessment, 6.1.3 Information security risk treatment, 8.2 Information security risk assessment and 8.3 Information security risk treatment 5.- A.9.2.3 Management of privileged access rights 6.- A.8.3.2 Disposal of media 7.- Clauses 9.1 Monitoring, measurement, analysis and evaluation and 10.1 Nonconformity and corrective action 8.- A.12.1.2 Change management (there is no control on this standard to manage specifically the configuration of CIs – Configuration Items) 9.- A.12.2.1 Controls against malware, and regarding to vulnerabilities you also have the A.12.6.1 Management of technical vulnerabilities and A.12.6.2 Restrictions on software installation 10.- A.13.1.1 Network controls, A.13.1.2 Security of networks services, A.13.1.3 Segregation in networks, and A.9.1.2 Access to networks and network services Finally, these articles related to cybersecurity can be interesting for you: “Which one to go with – Cybersecurity Framework or ISO 27001?” : https://advisera.com/27001academy/blog/2014/02/24/which-one-to-go-with-cybersecurity-framework-or-iso-27001/ “What is cybersecurity and how can ISO 27001 help?” : https://advisera.com/27001academy/blog/2011/10/25/what-is-cybersecurity-and-how-can-iso-27001-help/ “ISO 27001 vs. ISO 27032 cybersecurity standard” : https://advisera.com/27001academy/blog/2015/08/25/iso-27001-vs-iso-27032-cybersecurity-standard/ And this free eBook can be also interesting for you “9 Steps to Cybersecurity” : https://advisera.com/books/9-steps-to-cybersecurity-managers-information-security-manual/
  • ISO 27001 and cybersecurity


    How can ISO 27001 map up with challenges of Cyber Security and what strategies should an ISO organization deploy to prevent Malware/cyber security attacks ?
     

    Answer:

    There is no universal rule to map specifically the requirements of ISO 27001 with the cybersecurity, keep in mind that ISO 27001 is mainly focused on the protection of the information (establishes requirements for an Information Security Management System), and this standard can be applied to any environment where the information needs to be protected, including the cybersecurity, but it is not the unique. Anyway, if you want to work with ISO 27001 and the cybersecurity, can be very interesting ISO 27032, which is also an international standard, but related to the cybersecurity, and you can integrate both.
    Furthermore, if your company wants to protect from attacks related to the cybersecurity, can be an interesting option to implement ISO 27032, that how you know can be integrated with ISO 27001.
    Finally, these articles can be interesting for you:
    “Which one to go with – Cybersecurity Framework or ISO 27001?” : https://advisera.com/27001academy/blog/2014/02/24/which-one-to-go-with-cybersecurity-framework-or-iso-27001/
    “What is cybersecurity and how can ISO 27001 help?” : https://advisera.com/27001academy/blog/2011/10/25/what-is-cybersecurity-and-how-can-iso-27001-help/
    “ISO 27001 vs. ISO 27032 cybersecurity standard” : https://advisera.com/27001academy/blog/2015/08/25/iso-27001-vs-iso-27032-cybersecurity-standard/
    And of course, can be very interesting for you our free eBook “9 Steps to Cybersecurity” : https://advisera.com/books/9-steps-to-cybersecurity-managers-information-security-manual/
  • Confidentiality levels


    Could you please inform  of the recommended confidentiality levels along with the best practice for setting these for the documents within ISO 9001, 22301 & 27001.
     

    Answer:

    Yes, sure. Commonly there are 3 confidential levels (and 1 Public level which means that everyone can see the information): Confidential (top level), Restricted (medium), and Internal use (lowest level). And from my point of view, the best practice for setting these for documents is to develop an Information Classification Policy. You can find more information here “Information classification according to ISO 27001” : https://advisera.com/27001academy/blog/2014/05/12/information-classification-according-to-iso-27001/
  • Supplier Security Policy


    "Supplier assurance framework" I am not sure what would be the key points in that doc. what should i need to include in that doc.

     

    Answer:

    I am sorry but we do not have the document “Supplier assurance framework”, it is not mandatory by the standard and I am not sure what do you mean with this. To see a complete list of mandatory documents (and non mandatory), please read this article “List of mandatory documents required by ISO 27001 (2013 revision)” : https://advisera.com/27001academy/knowledgebase/list-of-mandatory-documents-required-by-iso-27001-2013-revision/
    If your question is related to the supplier security, this article can be interesting for you “6-step process for handling supplier security according to ISO 27001” : https://advisera.com/27001academy/blog/2014/06/30/6-step-process-for-handling-supplier-security-according-to-iso-27001/ 
    Finally keep in mind that the unique mandatory document related to the supplier security is the “Supplier Security Policy” (clause A.15.1.1 of the Annex A of the ISO 27001:2013).
  • Gap AnalysisISO 27001, version 2015?


    I would like to know how to tackle a GAP analiss 27001, whether it should be similar to an internal audit on the planning and documentation, or as external audit stage 2, wherein in step 1 focuses on documentaries and in step 2 in the-spot checks
    I solicitadno the company to acquire the full premium kid, I'm waiting for answers Manager.
     

    Answer:

    The Gap Analysis is more similar to the internal audit, with the difference that the gap is performed at the beginning of the project (when there is nothing implemented). Anyway the Gap analysis is not mandatory, but can be useful and if you want to do it you can use our free tool “Free ISO 27001 Gap Analysis Tool” : https://advisera.com/27001academy/free-iso-27001-gap-analysis-tool/
    Regarding your manager, my recommendation is that you need to show him the benefits of the implementation of the standard, so this article can be interesting for you “Four key benefits of ISO 27001 implementation” : https://advisera.com/27001academy/knowledgebase/four-key-benefits-of-iso-27001-implementation/-implement ation/
    Finally, if you want you can write us in Spanish.We have received these questions:



    Q1:Need the basic difference in the latest version of 2015
    Received links:
    - Infographic: New ISO 27001 2013 revision – What has changed? https://advisera.com/27001academy/knowledgebase/infographic-new-iso-27001-2013-revision-what-has-changed/
    - How to make a transition from ISO 27001 2005 revision to 2013 revision https://advisera.com/27001academy/knowledgebase/how-to-make-a-transition-from-iso-27001-2005-revision-to-2013-revision/
    Q2: Do we find any difference in the risk management area? 

     

    Answer:

    A1: I am sorry, but the latest version of the ISO 27001 is ISO 27001:2013. There is no ISO 27001:2015, although if your country has been translated the standard this year, you can see ISO/IEC 27001:2015, but with the code of your country at the beginning. For example, in Australia the ISO 27001 has been translated in 2015, so you can see the AS ISO/IEC 27001:2015, however it is the same that ISO/IEC 27001:2013 (all requirements are the same), but using Australian terminology.
    A2: There are some changes, but from my point of view one of the more important is that in ISO 27001:2013 you do not need to use the assets-threats-vulnerabilities methodology to identify risks. If you need more information about this, please read this article “What has changed in risk assessment in ISO 27001:2013” : https://advisera.com/27001academy/knowledgebase/what-has-changed-in-risk-assessment-in-iso-270012013/
  • Capacity Management Procedure


    To cite an example for capacity management procedure. Objective: To establish and implement controls to ensure capacity monitoring. Scope: This applies to all information and information processing facilities of [
  • Gap Analysis

    The gap analysis is not mandatory before the begin of the ISMS implementation according to ISO 27001:2013, although it can be very useful. The Gap analysis is about the requirements of ISO 27001, including the security controls of Annex A (that as you know are the same as the security controls of ISO 27002).

    To perform this activity, of course you can use CMMI levels to assess the compliance of each requirement, and you can also use our free tool "Free ISO 27001 Gap Analysis Tool" :https://advisera.com/27001academy/free-iso-27001-gap-analysis-tool/
  • Assets value

    From my point of view both approaches can be good for the standard, however taking the average does not make sense - it is much better to take the highest value from the C-I-A impact, and it is not necessary to consider the evaluation of each asset value: you can consider the assessment of consequences for the materialization of a risk , and the assessment of likelihood of occurrence of such risk.
    Have you seen our free webinar about "The basics of risk assessment and treatment according to ISO 27001" ? : https://advisera.com/27001academy/webinar/basics-risk-assessment-treatment-according-iso-27001-free-webinar-demand/
    This article can be also interesting for you “ISO 2701 risk assessment: How to match assets, threats and vulnerabilities” : https://advisera.com/27001academy/knowledgebase/iso-27001-risk-assessment-how-to-match-assets-threats-and-vulnerabilities/
Page 1051-vs-13485 of 1127 pages

Didn’t find an answer?

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

CREATE NEW TOPIC +