data.gift
  • Datasets

http://cyfun.data.gift/data/requirement_GV_RM_05_1

http://cyfun.data.gift/data/requirement_GV_RM_05_1
Concept

  • http://cyfun.data.gift/data/CyFun2025

    • External link
    • Internal link
  • http://cyfun.data.gift/data/CyFun2025_delta_BASIC_to_IMPORTANT

    • External link
    • Internal link
  • http://cyfun.data.gift/data/CyFun2025_IMPORTANT

    • External link
    • Internal link
  • http://cyfun.data.gift/data/CyFun2025_ESSENTIAL

    • External link
    • Internal link

  • http://cyfun.data.gift/data/subcategory_GV.RM-05

    • External link
    • Internal link

Properties and relations

Direct links from the subject.

Property Value

type

The subject is an instance of a class.

  • External link
  • Internal link

http://cyfun.data.gift/ontology#Requirement

  • External link
  • Internal link

type

The subject is an instance of a class.

  • External link
  • Internal link

Concept

An idea or notion; a unit of thought.

  • External link
  • Internal link

label

A human-readable name for the subject.

  • External link
  • Internal link

GV.RM-05.1: To support the high-level risk management vision, the organisation shall establish clear lines of communication for cybersecurity risks, including those arising from suppliers and third parties.

http://cyfun.data.gift/ontology#requirementId

  • External link
  • Internal link

GV.RM-05.1

http://cyfun.data.gift/ontology#foundIn

  • External link
  • Internal link

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p22

  • External link
  • Internal link

http://cyfun.data.gift/ontology#foundIn

  • External link
  • Internal link

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p19

  • External link
  • Internal link

has broader

Relates a concept to a concept that is more general in meaning.

  • External link
  • Internal link

http://cyfun.data.gift/data/subcategory_GV.RM-05

  • External link
  • Internal link

note

A general note, for any purpose.

  • External link
  • Internal link

The aim of this control is to ensure that cybersecurity and information security risk information is shared effectively across the organisation and with external parties. This control focus on operational and tactical communication is specific to cybersecurity risks and emphasises communication channels (e.g., reporting, escalation, coordination), including external risks from suppliers and third parties. Consider the following elements when implementing this control: - Define Communication Roles and Responsibilities Assign clear ownership for reporting, escalating, and responding to cybersecurity risks across departments and with third parties. - Establish Communication Channels Use structured channels such as email groups, ticketing systems, incident response platforms, orcollaboration tools (e.g. Teams, Slack) for timely risk communication. - Include Third Parties Integrate suppliers and partners into the communication process through contractual clauses, shared report- ing protocols, or joint incident response plans. - Document and Train Maintain a communication protocol or playbook and train relevant staff on how and when to report cyber- security risks. - Review and Improve Periodicallytest and reviewcommunication effectiveness through tabletop exercises orpost-incident reviews. This control supports the implementation of GV.RM-03.2 by ensuring that identified and documented risks are communicated to the right stakeholders, enabling timely response and coordination. GOVERN C BILITIES,AND

note

A general note, for any purpose.

  • External link
  • Internal link

<div><p>The aim of this control is to ensure that cybersecurity and information security risk information is shared effectively across the organisation and with external parties. This control focus on operational and tactical communication is specific to cybersecurity risks and emphasises communication channels (e.g., reporting, escalation, coordination), including external risks from suppliers and third parties. Consider the following elements when implementing this control:</p><ul><li>Define Communication Roles and Responsibilities Assign clear ownership for reporting, escalating, and responding to cybersecurity risks across departments and with third parties.</li><li>Establish Communication Channels Use structured channels such as email groups, ticketing systems, incident response platforms, orcollaboration tools (e.g. Teams, Slack) for timely risk communication.</li><li>Include Third Parties Integrate suppliers and partners into the communication process through contractual clauses, shared report- ing protocols, or joint incident response plans.</li><li>Document and Train Maintain a communication protocol or playbook and train relevant staff on how and when to report cyber- security risks.</li><li>Review and Improve Periodicallytest and reviewcommunication effectiveness through tabletop exercises orpost-incident reviews. This control supports the implementation of GV.RM-03.2 by ensuring that identified and documented risks are communicated to the right stakeholders, enabling timely response and coordination. GOVERN C BILITIES,AND</li></ul></div>

note

A general note, for any purpose.

  • External link
  • Internal link

The aim of this control is to ensure that cybersecurity and information security risk information is shared effectively across the organisation and with external parties. This control focus on operational and tactical communication is specific to cybersecurity risks and emphasises communication channels (e.g., reporting, escalation, coordination), including external risks from suppliers and third parties. Consider the following elements when implementing this control: • Define Communication Roles and Responsibilities Assign clear ownership for reporting, escalating, and responding to cybersecurity risks across departments and with third parties. • Establish Communication Channels Use structured channels such as email groups, ticketing systems, incident response platforms, orcollaboration tools (e.g. Teams, Slack) for timely risk communication. • Include Third Parties Integrate suppliers and partners into the communication process through contractual clauses, shared report- ing protocols, or joint incident response plans. • Document and Train Maintain a communication protocol or playbook and train relevant staff on how and when to report cyber- security risks. • Review and Improve Periodicallytest and reviewcommunication effectiveness through tabletop exercises orpost-incident reviews. This control supports the implementation of GV.RM-03.2 by ensuring that identified and documented risks are communicated to the right stakeholders, enabling timely response and coordination. GOVERN C BILITIES,AND

note

A general note, for any purpose.

  • External link
  • Internal link

The aim of this control is to ensure that cybersecurity and information security risk information is shared effectively across the organisation and with external parties. This control focus on operational and tactical communication is specific to cybersecurity risks and emphasises communication channels (e.g., reporting, escalation, coordination), including external risks from suppliers and third parties. Consider the following elements when implementing this control: - Define Communication Roles and Responsibilities Assign clear ownership for reporting, escalating, and responding to cybersecurity risks across departments and with third parties. - Establish Communication Channels Use structured channels such as email groups, ticketing systems, incident response platforms, orcollaboration tools (e.g. Teams, Slack) for timely risk communication. - Include Third Parties Integrate suppliers and partners into the communication process through contractual clauses, shared report- ing protocols, or joint incident response plans. - Document and Train Maintain a communication protocol or playbook and train relevant staff on how and when to report cyber- security risks. - Review and Improve Periodicallytest and reviewcommunication effectiveness through tabletop exercises orpost-incident reviews. This control supports the implementation of GV.RM-03.2 by ensuring that identified and documented risks are communicated to the right stakeholders, enabling timely response and coordination. GOVERN C BILITIES,AND

notation

A notation, also known as classification code, is a string of characters such as "T58.5" or "303.4833" used to uniquely identify a concept within the scope of a given concept scheme.

  • External link
  • Internal link

GV.RM-05.1

alternative label

skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties.

  • External link
  • Internal link

Risk communication channels

preferred label

A resource has no more than one value of skos:prefLabel per language tag, and no more than one value of skos:prefLabel without language tag.

  • External link
  • Internal link

To support the high-level risk management vision, the organisation shall establish clear lines of communication for cybersecurity risks, including those arising from suppliers and third parties.

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

  • External link
  • Internal link

http://cyfun.data.gift/data/CyFun2025

  • External link
  • Internal link

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

  • External link
  • Internal link

http://cyfun.data.gift/data/CyFun2025_delta_BASIC_to_IMPORTANT

  • External link
  • Internal link

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

  • External link
  • Internal link

http://cyfun.data.gift/data/CyFun2025_IMPORTANT

  • External link
  • Internal link

is in scheme

Relates a resource (for example a concept) to a concept scheme in which it is included.

  • External link
  • Internal link

http://cyfun.data.gift/data/CyFun2025_ESSENTIAL

  • External link
  • Internal link

http://cyfun.data.gift/ontology#level

  • External link
  • Internal link

http://cyfun.data.gift/data/level_IMPORTANT

  • External link
  • Internal link

triple count

The number of triples associated with the subject.

  • External link
  • Internal link

19

in dataset

Specifies the dataset the subject is part of.

  • External link
  • Internal link

http://data.gift/d/datasets/69E8863AA6CE46D9ACD13109

  • External link
  • Internal link

Resultaten 1 - 21 of 21

References

Inverse links to the subject.

Property Subject

http://cyfun.data.gift/ontology#hasRequirement

  • External link
  • Internal link

http://cyfun.data.gift/data/subcategory_GV.RM-05

  • External link
  • Internal link

has narrower

Relates a concept to a concept that is more specific in meaning.

  • External link
  • Internal link

http://cyfun.data.gift/data/subcategory_GV.RM-05

  • External link
  • Internal link

Resultaten 1 - 1 of 1

© 2024 redpencil.io. All rights reserved.