--- title: Registering Service Continuity Scope slug: helium-en/registering-service-continuity-scope description: Learn about the Continuity Registration process and its phases including initiation, risk evaluation, and compliance with ISO 27001. Discover the prerequisites for starting the process and the procedure for linking the scope to a specific continuity. createdAt: 2021-10-18T19:29:33.000Z --- ******Continuity Registration** is a process that passes through several phases. The first step of this process, Initiation, is where the policy, scope and project and IT service continuity will be defined. This functionality allows registering the continuity scope. It is necessary to set the scope and team responsibilities, covering the process activities, such as risk evaluation, business impact analysis (BIA), determination of controls according to the customer and regulatory requirements, considering audit points, and compliance with ISO 27001. ## Before getting started - [x] The existence of a defined service in the Portfolio and Catalog Management process. - [x] It is necessary to have registered the Continuity Registration and define the service continuity policy. - [x] It is essential to have registered the threat and threat category, both linked to each other. In addition, have registered the risk and risk category. - [x] It is equally necessary to register the automatic actions of Incident, Request, and Procedure about the Event Management. ## Procedure 1. Access the functionality through the main menu `Processes > Continuity Management > Continuity`; 2. Find the continuity you want to link the scope and click on "**Advance**"; 3. In **Initiation**, click on "**Scope**" and then on the tab "**Scope**"; 4. Complete the fields necessary: Executive summary and description; 5. To attach a file, click on the "**Attach**" tab and then on "**Add file**" to link it; 6. Click on "**Save**".