Search results

Home / Search

Category:
Select
Select

11277 results

Guest

Guest

Create New Topic As guest or Sign in

HTML tags are not allowed

Select

Assign topic to the user

  • Business Continuity Plan Testing Exercise

    1 - Can we include Risk assessment and BIA in the test exercise and ask questions on that? or in other words should we do both analyses during this testing exercise?

    Please note that the purpose of a BC Plan tabletop exercise is to assess the effectiveness of the devised plan (e.g., if people know what to do, if all required activities are included and well described, etc.), not to evaluate it against BIA and risks, so both analyses should not be performed together (this would only make the test unnecessarily complex).

    Considering that, the best course of action would be to ask for the information about BIA and risk assessment, and evaluate the BC Plan before the test, and if this information is not available you could explain that without a clear understanding of business impacts and associated risks, even though the BC Plan test is considered successful, it may not be fully aligned with the relevant impacts and risks related to the considered scenario.

    For further information about BC Plan tests, see:

    2 - Secondly, what are the most relevant questions we should be asking?

    A tabletop exercise means testing a plan by means of team interaction, so examples of relevant questions to be asked to people involved in the BC Plan would be related to:

    • the sequence of activities to be performed by each person in case of a Data Centre Power Outage
    • the means of communication to be used, who to communicate to, and what to communicate
    • the knowledge of each person about the activities other members will be performing

    Based on these questions, and the speed and confidence of response, you can evaluate if the involved personnel are familiar with the plan and can perform it in a satisfactory way.

  • 27001 Certification for Multiple Companies / Geographic locations

    1 - I'm struggling to get my head around how we can justify scoping out the IT Management side of the Company. The IT Management side will have complete control of our IT systems and potentially uncontrolled access to our servers. If we establish contracts or service agreements, won't the security requirements be the majority (if not all) of Site A's ISMS? If so, what's the benefit of scoping them out?

    Please note that security requirements defined for Site A can be also enforced on Site B by means of contracts/service agreements. The benefits of scoping out the IT management are related to decreasing the complexity of the scope and certification maintenance costs since you will have a smaller scope to manage.  

    Regarding control of the IT infrastructure by Site B, it can be legally defined (through contract/service agreement) that any decision it makes needs approval from Headquarters to be implemented, so even though it has operational control, it will not have the decision power to implement changes without HQ consent.

    Regarding the risk of uncontrolled access to your servers, controls such as encryption, logging, and monitoring of the user administrator’s activities can be used to decrease such risks.  

    For further information, see:

    • Which security clauses to use for supplier agreements? https://advisera.com/27001academy/blog/2017/06/19/which-security-clauses-to-use-for-supplier-agreements/

    2 - Would considering Site A and Site B as one Company but Site B (still providing IT Management and Design services) scoped out of ISMS be an easier way to implement the ISMS? Site B will still implement the relevant ISMS policies but only Site A will be certified? I'm thinking this might save a somewhat complicated contract/service agreement and less controls to be audited.

    The scenarios considering Site A and Site B as different companies, and both as the same company but with Site B scoped out of ISMS would be the same for an ISO 27001 certification, i.e., you would still need to develop an agreement between them, since they will have the same client-supplier relation.

    In fact, this situation would be a bit more complex, because you would need to align first with the certification body the situation of having two legally different organizations considered as a single company.

    3 - Lastly, I understand that the Chief of Information Security type role is not mandatory under 27001 but it is beneficial to the process. Is it possible for someone from Site B to take this position for Site A despite being scoped as a third party?

    ISO 27001 does not prescribe that information security roles need to be fulfilled by an organization’s employee, so provided you can evidence that the related roles are defined and being fulfilled, you can “outsource” this position to someone from Site B.

  • Auditor definition

    As long as Jack does not audit his own work, there is no conflict of interest in this scenario, even if John and Jack have the same boss.

    This article will provide you with further explanation about internal audit:

    These materials will also help you regarding internal audit:

  • Certifications merge

    This situation needs to be evaluated by the certification bodies that issued the certifications, so you should contact them to receive proper clarification.

    Technically speaking, the “merge” would mean an update in the scope of the certification that would receive the merged certification, and all sequential steps after a scope update (e.g., review of risks, implemented controls, etc.).

    This article will provide you with further explanation about integrated management systems:

  • BCMS | ISO 22301:2019

    The duration of the implementation project varies according to many variables (e.g., available resources, experience with standard requirements, top management involvement, etc.), but for companies of up to 200 employees the implementation time is up to 8 months.

    To get an insight into the time duration for your organization, please read (although the material is about ISO 27001, the same concepts apply to ISO 22301):

    • Time, effort and roles for the implementation https://advisera.com/27001academy/knowledgebase/iso-27001-implementation-checklist/#effort

    • Entry into the IT department

      1 - I will like to know if iso 27001 standard talks about a single point of entry into the IT department. I will like to know if ISO27001 talks about multiple entries into the IT department and best practices.

      I’m assuming that by “single point of entry into the IT department” you mean physical access to the department.

      Considering that, ISO 27001 does not provide specifics about the implementation of security controls. It only provides a general description of the controls.

      In general terms, physical single and multiple points of entry into the IT department fall into Annex A control A.11.1.2 (Physical entry controls), as ways to implement this control.  

      For further information, see:

      2 - if not, what standard should I look out for

      For guidance on the implementation of ISO 27001 security controls, you should look for ISO 27002, which provides guidance on the implementation of ISO 27001 Annex A controls.

      This article will provide you with further explanation about ISO 27002:

    • Supplier Security Policy Question

      The Supplier Security Policy applies to all companies that provide or will provide services to your company, but not to your customers (customer requirements are handled through the List of Legal, Statutory, and Contractual requirements template, located in folder 2 Identification of Requirements).

      This article will provide you with further explanation about suppliers’ security:

      • 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/

      • Backup and DR plans - outsourced services

        Please note that RTOs are usually set at the department level, while RPOs are set at the application level.

        Considering that you do not need to define a specific RTO for each application. They will inherit the RTO from the business departments they are related to.

        Regarding the RPO, you can group them according to their criticality or other predefined criteria (e.g., belonging to the same department or process, having a similar RPO) and defining a single RPO for the whole group. Therefore, you will have a different RPO for each of your 3 categories of applications.

        This would make your administration job easier. But you need to evaluate the impact of adopting general RTOs/RPOs considering the allocation of resources and fulfillment of legal requirements. 

        These articles will provide you with further explanation about RPO and RTO:

        • What is the difference between Recovery Time Objective (RTO) and Recovery Point Objective (RPO)? https://advisera.com/27001academy/knowledgebase/what-is-the-difference-between-recovery-time-objective-rto-and-recovery-point-objective-rpo/
        • Explanation of the most common business continuity terms https://advisera.com/27001academy/blog/2021/01/18/explanation-of-most-common-business-continuity-terms/

        • ISO 27001 Scope Document

          1 - Do we need to show network documentation of all offices in the ISMS scope, or can we put reference links to the documentation?

          For the ISMS scope document, there is no need to show network documentation, but if you want you can include reference links to detailed documentation. 

          2 - Do we need to include network diagrams of each office in the ISMS scope document?

          There is no need to include high-level topology diagrams, but if you want you can include reference like those included on page 5 of each of your documents to give an overview of the network topology.

          3 - Do we need to include the XYZ1 office in the scope as the whole outsourcing department works from XYZ2, and it's only the senior managers like the CEO and Founder who work from  XYZ1 including the IT security administrator?

          Yes, you should include the XYZ1 office in the scope, or at least the part of the office with senior management and the IT security administrator.

          4 - Will the ISMS scope focus on the outsourcing department's IT infrastructure be enough, or do we need to implement the ISMS scope to cover the *** IT operations infrastructure across the business?

          This answer will depend on the information you want to protect. In case you want to protect the information handled and processed by ***, then you need to include the IT operations infrastructure that runs across the business. If this is not the case, then the scope covering the Outsourcing departments will be enough.

        • SOA Control Objectives

          The controls listed in the SoA template included in the ISO 27001:2022 toolkit are the same ones defined in the ISO 27002:2022.

          Please note that the column “Control Objectives” needs to be filled in by the organization. Control objectives are not mandatory in SoA, but including them in the SoA will make it easier to follow them, and reduce administrative effort to keep them in a separate document.

          These articles will provide you with further explanation about ISO 27001 and ISO 27002 controls:

Page 65-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 +