Watchtower/Law library/Network and Information Systems.../12 Relevant digital service providers
As last captured

Network and Information Systems Regulations 2018 · PART 4 Digital Services

12 Relevant digital service providers

reg. 12 · in force: yes

Captured statutory text (L5)

12 Relevant digital service providers

(1)A RDSP must identify and take appropriate and proportionate measures to manage the risks posed to the security of network and information systems on which it relies to provide, within the United Kingdom, the following services—
(a)online marketplace;
(b)online search engine; or
(c)cloud computing service.
(2)The measures taken by a RDSP under paragraph (1) must—
(a)(having regard to the state of the art) ensure a level of security of network and information systems appropriate to the risk posed;
(b)prevent and minimise the impact of incidents affecting their network and information systems with a view to ensuring the continuity of those services; and
(c)take into account the following elements as specified in Article 2 of EU Regulation 2018/151—
(i)the security of systems and facilities;
(ii)incident handling;
(iii)business continuity management;
(iv)monitoring auditing and testing; and
(v)compliance with international standards.
(3)A RDSP must notify the Information Commission in writing about any incident having a substantial impact on the provision of any of the digital services mentioned in paragraph (1) that it provides.
(4)The requirement to notify in paragraph (3) applies only if the RDSP has access to information which enables it to assess whether the impact of an incident is substantial.
(5)The notification mentioned in paragraph (3) must provide the following information—
(a)the RDSP’s name and the digital services that it provides;
(b)the time the ... incident occurred;
(c)the duration of the ... incident;
(d)information concerning the nature and impact of the ... incident;
(e)information concerning any, or any likely, cross-border impact of the ... incident; and
(f)any other information that may be helpful to the Information Commission.
(6)The notification under paragraph (3) must—
(a)be made without undue delay and in any event no later than 72 hours after the RDSP is first aware that an incident has occurred; and
(b)contain sufficient information to enable the Information Commission to determine the significance of any cross-border impact.
(7)In order to determine whether the impact of an incident is substantial the RDSP must—
(a)take into account the following parameters, as specified in Article 3 of EU Regulation 2018/151—
(i)the number of users affected by the incident and, in particular, the users relying on the digital service for the provision of their own services;
(ii)the duration of the incident;
(iii)the geographical area affected by the incident;
(iv)the extent of the disruption to the functioning of the service;
(v)the extent of the impact on economic and societal activities; and
(b)have regard to any relevant guidance published by the Information Commission.
(8)After receipt of a notification under paragraph (3) the Information Commission must share the incident notification with the CSIRT as soon as reasonably practicable.
(9)If an OES is reliant on a RDSP to provide an essential service, the operator must notify the designated competent authority for the OES in writing in relation to it about any significant impact on the continuity of the service it provides caused by an incident affecting the RDSP without undue delay.
(10). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(11)The Information Commission is not required to share information under these Regulations if the information contains—
(a)confidential information; or
(b)information which may prejudice the security or commercial interests of a RDSP.
(12)If the Information Commission or CSIRT—
(a)consults with the RDSP responsible for an incident notification under paragraph (3), and
(b)is of the view that public awareness about that incident is necessary to prevent or manage it, or is in the public interest,
the Information Commission or CSIRT may inform the public about that incident or the Information Commission may direct the RDSP responsible for the notification to do so.
(13)Before the Information Commission or CSIRT informs the public about an incident notified under paragraph (3), the Information Commission or CSIRT must consult each other and the RDSP who provided the notification.
(14)The Information Commission may inform the public about an incident affecting digital services in a Member State of the EU if—
(a)the relevant authorities in the affected Member State notify the Information Commission about the incident;
(b)the Information Commission consults with those relevant authorities; and
(c)the Information Commission is of the view mentioned in paragraph (12)(b).
(15)The Information Commission must provide an annual report to the SPOC identifying the number and nature of incidents notified to it under paragraph (3).
(16)The first report mentioned in paragraph (15) must be submitted on or before 1st July 2018 and subsequent reports must be submitted at annual intervals after that date.
(17). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Full captured verbatim text
(1) A RDSP must identify and take appropriate and proportionate measures to manage the risks posed to the security of network and information systems on which it relies to provide, within the United Kingdom, the following services—

(a) online marketplace;

(b) online search engine; or

(c) cloud computing service.

(2) The measures taken by a RDSP under paragraph (1) must—

(a) (having regard to the state of the art) ensure a level of security of network and information systems appropriate to the risk posed;

(b) prevent and minimise the impact of incidents affecting their network and information systems with a view to ensuring the continuity of those services; and

(c) take into account the following elements as specified in Article 2 of EU Regulation 2018/151—

(i) the security of systems and facilities;

(ii) incident handling;

(iii) business continuity management;

(iv) monitoring auditing and testing; and

(v) compliance with international standards.

(3) A RDSP must notify the Information Commission in writing about any incident having a substantial impact on the provision of any of the digital services mentioned in paragraph (1) that it provides.

(4) The requirement to notify in paragraph (3) applies only if the RDSP has access to information which enables it to assess whether the impact of an incident is substantial.

(5) The notification mentioned in paragraph (3) must provide the following information—

(a) the RDSP’s name and the digital services that it provides;

(b) the time the ... incident occurred;

(c) the duration of the ... incident;

(d) information concerning the nature and impact of the ... incident;

(e) information concerning any, or any likely, cross-border impact of the ... incident; and

(f) any other information that may be helpful to the Information Commission.

(6) The notification under paragraph (3) must—

(a) be made without undue delay and in any event no later than 72 hours after the RDSP is first aware that an incident has occurred; and

(b) contain sufficient information to enable the Information Commission to determine the significance of any cross-border impact.

(7) In order to determine whether the impact of an incident is substantial the RDSP must—

(a) take into account the following parameters, as specified in Article 3 of EU Regulation 2018/151—

(i) the number of users affected by the incident and, in particular, the users relying on the digital service for the provision of their own services;

(ii) the duration of the incident;

(iii) the geographical area affected by the incident;

(iv) the extent of the disruption to the functioning of the service;

(v) the extent of the impact on economic and societal activities; and

(b) have regard to any relevant guidance published by the Information Commission.

(8) After receipt of a notification under paragraph (3) the Information Commission must share the incident notification with the CSIRT as soon as reasonably practicable.

(9) If an OES is reliant on a RDSP to provide an essential service, the operator must notify the designated competent authority for the OES in writing in relation to it about any significant impact on the continuity of the service it provides caused by an incident affecting the RDSP without undue delay.

(10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

(11) The Information Commission is not required to share information under these Regulations if the information contains—

(a) confidential information; or

(b) information which may prejudice the security or commercial interests of a RDSP.

(12) If the Information Commission or CSIRT—

(a) consults with the RDSP responsible for an incident notification under paragraph (3), and

(b) is of the view that public awareness about that incident is necessary to prevent or manage it, or is in the public interest,

the Information Commission or CSIRT may inform the public about that incident or the Information Commission may direct the RDSP responsible for the notification to do so.

(13) Before the Information Commission or CSIRT informs the public about an incident notified under paragraph (3), the Information Commission or CSIRT must consult each other and the RDSP who provided the notification.

(14) The Information Commission may inform the public about an incident affecting digital services in a Member State of the EU if—

(a) the relevant authorities in the affected Member State notify the Information Commission about the incident;

(b) the Information Commission consults with those relevant authorities; and

(c) the Information Commission is of the view mentioned in paragraph (12)(b).

(15) The Information Commission must provide an annual report to the SPOC identifying the number and nature of incidents notified to it under paragraph (3).

(16) The first report mentioned in paragraph (15) must be submitted on or before 1st July 2018 and subsequent reports must be submitted at annual intervals after that date.

(17) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

What this provision means

Model summary, checked against the text on the left.

Relevance to Signicat: 2/3 · detailed summary (L4) Status: ok · Stored artifact; current recipe verification unavailable

RDSPs must implement security measures for network systems and report substantial impact incidents to the Information Commission within 72 hours.

(3) A RDSP must notify the Information Commission in writing about any incident having a substantial impact on the provision of any of the digital services mentioned in paragraph (1) that it provides.
(4) The requirement to notify in paragraph (3) applies only if the RDSP has access to information which enables it to assess whether the impact of an incident is substantial.
(a) be made without undue delay and in any event no later than 72 hours after the RDSP is first aware that an incident has occurred; and
A RDSP must take appropriate and proportionate security measures under (1) to manage risks to network and information systems for online marketplaces, search engines, or cloud computing services. Under (3), it must notify the Information Commission in writing about any substantial impact incident without undue delay and no later than 72 hours after becoming aware, providing the details listed in (5). Under (9), an OES reliant on a RDSP must notify its designated competent authority of significant impacts without undue delay.
evidence.audit_trail

Refers to

No captured references.

Referred to by

cross-reference internal_cite · reg. 13

cross-reference internal_cite · reg. 17

cross-reference internal_cite · reg. 4

cross-reference internal_cite · reg. 5

Part summaries

0 of 0 parts have a verified summary.

L1 unavailable for current verification: the overall summary needs every part verified. Provisions and the verified summaries remain readable.

Verification findings (48)

synthesis coverage: missing/unverified L2 part-1

synthesis coverage: missing evaluation uk:uksi/2018/506#regulation-1

synthesis coverage: missing/unverified L2 part-2

synthesis coverage: missing evaluation uk:uksi/2018/506#regulation-2

synthesis coverage: missing evaluation uk:uksi/2018/506#regulation-3

synthesis coverage: missing evaluation uk:uksi/2018/506#regulation-4

synthesis coverage: missing evaluation uk:uksi/2018/506#regulation-5

synthesis coverage: missing evaluation uk:uksi/2018/506#regulation-6

synthesis coverage: missing evaluation uk:uksi/2018/506#regulation-7

synthesis coverage: missing/unverified L2 part-3

synthesis coverage: missing evaluation uk:uksi/2018/506#regulation-8

synthesis coverage: missing evaluation uk:uksi/2018/506#regulation-8A

synthesis coverage: missing evaluation uk:uksi/2018/506#regulation-9

synthesis coverage: missing evaluation uk:uksi/2018/506#regulation-10

synthesis coverage: missing evaluation uk:uksi/2018/506#regulation-11

synthesis coverage: missing/unverified L2 part-4

synthesis coverage: missing evaluation uk:uksi/2018/506#regulation-12

synthesis coverage: missing evaluation uk:uksi/2018/506#regulation-13

synthesis coverage: missing evaluation uk:uksi/2018/506#regulation-14

synthesis coverage: missing evaluation uk:uksi/2018/506#regulation-14A

synthesis coverage: missing/unverified L2 part-5

synthesis coverage: missing evaluation uk:uksi/2018/506#regulation-15

synthesis coverage: missing evaluation uk:uksi/2018/506#regulation-16

synthesis coverage: missing evaluation uk:uksi/2018/506#regulation-17

synthesis coverage: missing evaluation uk:uksi/2018/506#regulation-18

synthesis coverage: missing evaluation uk:uksi/2018/506#regulation-19

synthesis coverage: missing evaluation uk:uksi/2018/506#regulation-19A

synthesis coverage: missing evaluation uk:uksi/2018/506#regulation-19B

synthesis coverage: missing evaluation uk:uksi/2018/506#regulation-A20

synthesis coverage: missing evaluation uk:uksi/2018/506#regulation-20

synthesis coverage: missing/unverified L2 part-6

synthesis coverage: missing evaluation uk:uksi/2018/506#regulation-21

synthesis coverage: missing evaluation uk:uksi/2018/506#regulation-22

synthesis coverage: missing evaluation uk:uksi/2018/506#regulation-23

synthesis coverage: missing evaluation uk:uksi/2018/506#regulation-24

synthesis coverage: missing evaluation uk:uksi/2018/506#regulation-25

synthesis coverage: missing/unverified L2 schedule-2

synthesis coverage: missing evaluation uk:uksi/2018/506#schedule-2-paragraph-1

synthesis coverage: missing evaluation uk:uksi/2018/506#schedule-2-paragraph-2

synthesis coverage: missing evaluation uk:uksi/2018/506#schedule-2-paragraph-3

synthesis coverage: missing evaluation uk:uksi/2018/506#schedule-2-paragraph-4

synthesis coverage: missing evaluation uk:uksi/2018/506#schedule-2-paragraph-5

synthesis coverage: missing evaluation uk:uksi/2018/506#schedule-2-paragraph-6

synthesis coverage: missing evaluation uk:uksi/2018/506#schedule-2-paragraph-7

synthesis coverage: missing evaluation uk:uksi/2018/506#schedule-2-paragraph-8

synthesis coverage: missing evaluation uk:uksi/2018/506#schedule-2-paragraph-9

synthesis coverage: missing evaluation uk:uksi/2018/506#schedule-2-paragraph-10

Instrument tier unavailable

Change history as published

Reg. 19 omitted (31.12.2020) by virtue of The Network and Information Systems (Amendment and Transitional Provision etc.) Regulations 2020 (S.I. 2020/1245), regs. 1(1), 15 (with reg. 21)

Pending effects amendments not yet applied to this text

Sch. 2 para. 4(5)(b) substituted by The Aviation Security (Amendment, Revocation and Consequential Provision) Regulations 2026 reg. 7(2) · Effective date unknown · Sch. 2 para. 4

Provenance

Every claim the system makes about this text is traceable to these identifiers.

Instrument
uk:uksi/2018/506
Part
PART 4 Digital Services
Version
77a3b4cc2fff325c17588c47…
Content hash
sha256 e3fcb79294db10298b8e1f86…
Source
legislation.gov.uk/uksi/2018/506