data.gift
  • Datasets

http://cyfun.data.gift/data/requirement_PR_AT_01_3

http://cyfun.data.gift/data/requirement_PR_AT_01_3
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_PR.AT-01

    • 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

PR.AT-01.3: Personnel shall receive training to understand their specific roles, responsibilities, and priorities during a cybersecurity or information security incident, including the steps they need to follow to respond effectively.

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

  • External link
  • Internal link

PR.AT-01.3

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

  • External link
  • Internal link

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p105

  • External link
  • Internal link

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

  • External link
  • Internal link

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p75

  • 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_PR.AT-01

  • External link
  • Internal link

note

A general note, for any purpose.

  • External link
  • Internal link

Thegoalofthiscontrolistoensurethatallpersonnelunderstandtheirspecificroles,responsibilities,andpriorities during a cybersecurityorinformation securityincident, enabling them to respond effectivelyand in coordination withtheorganisation’sincidentresponseandcontingencyplans.Thiscontrolbuildsonthethreat-specificaware- ness from PR.AT-01.2 by introducing role-based training and incident response readiness. The implementation should consider the following: • Training should be tailored to different roles (e.g., IT, HR, executives) so that each group understands its specific responsibilities during an incident. • Personnel should be familiarwith theirobjectives, recoverypriorities, and the correct orderof actions to take during an incident. • Tabletop exercises orsimulated drills should be used to practice incident response in a realistic but controlled environment. • Clear documentation should be provided outlining each role’s tasks and responsibilities during an incident. • Training should explain how incident response connects to contingency planning, ensuring that staff under- stand when and how to activate contingency measures (see also ID.IM-04.1). • Regular refresher sessions should be held to keep knowledge up to date and reinforce readiness.

note

A general note, for any purpose.

  • External link
  • Internal link

Thegoalofthiscontrolistoensurethatallpersonnelunderstandtheirspecificroles,responsibilities,andpriorities during a cybersecurityorinformation securityincident, enabling them to respond effectivelyand in coordination withtheorganisation’sincidentresponseandcontingencyplans.Thiscontrolbuildsonthethreat-specificaware- ness from PR.AT-01.2 by introducing role-based training and incident response readiness. The implementation should consider the following: - Training should be tailored to different roles (e.g., IT, HR, executives) so that each group understands its specific responsibilities during an incident. - Personnel should be familiarwith theirobjectives, recoverypriorities, and the correct orderof actions to take during an incident. - Tabletop exercises orsimulated drills should be used to practice incident response in a realistic but controlled environment. - Clear documentation should be provided outlining each role’s tasks and responsibilities during an incident. - Training should explain how incident response connects to contingency planning, ensuring that staff under- stand when and how to activate contingency measures (see also ID.IM-04.1). - Regular refresher sessions should be held to keep knowledge up to date and reinforce readiness.

note

A general note, for any purpose.

  • External link
  • Internal link

Thegoalofthiscontrolistoensurethatallpersonnelunderstandtheirspecificroles,responsibilities,andpriorities during a cybersecurityorinformation securityincident, enabling them to respond effectivelyand in coordination withtheorganisation’sincidentresponseandcontingencyplans.Thiscontrolbuildsonthethreat-specificaware- ness from PR.AT-01.2 by introducing role-based training and incident response readiness. The implementation should consider the following: - Training should be tailored to different roles (e.g., IT, HR, executives) so that each group understands its specific responsibilities during an incident. - Personnel should be familiarwith theirobjectives, recoverypriorities, and the correct orderof actions to take during an incident. - Tabletop exercises orsimulated drills should be used to practice incident response in a realistic but controlled environment. - Clear documentation should be provided outlining each role’s tasks and responsibilities during an incident. - Training should explain how incident response connects to contingency planning, ensuring that staff under- stand when and how to activate contingency measures (see also ID.IM-04.1). - Regular refresher sessions should be held to keep knowledge up to date and reinforce readiness.

note

A general note, for any purpose.

  • External link
  • Internal link

<div><p>Thegoalofthiscontrolistoensurethatallpersonnelunderstandtheirspecificroles,responsibilities,andpriorities during a cybersecurityorinformation securityincident, enabling them to respond effectivelyand in coordination withtheorganisation’sincidentresponseandcontingencyplans.Thiscontrolbuildsonthethreat-specificaware- ness from PR.AT-01.2 by introducing role-based training and incident response readiness. The implementation should consider the following:</p><ul><li>Training should be tailored to different roles (e.g., IT, HR, executives) so that each group understands its specific responsibilities during an incident.</li><li>Personnel should be familiarwith theirobjectives, recoverypriorities, and the correct orderof actions to take during an incident.</li><li>Tabletop exercises orsimulated drills should be used to practice incident response in a realistic but controlled environment.</li><li>Clear documentation should be provided outlining each role’s tasks and responsibilities during an incident.</li><li>Training should explain how incident response connects to contingency planning, ensuring that staff under- stand when and how to activate contingency measures (see also ID.IM-04.1).</li><li>Regular refresher sessions should be held to keep knowledge up to date and reinforce readiness.</li></ul></div>

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

PR.AT-01.3

alternative label

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

  • External link
  • Internal link

Incident role-specific training

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

Personnel shall receive training to understand their specific roles, responsibilities, and priorities during a cybersecurity or information security incident, including the steps they need to follow to respond effectively.

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_PR.AT-01

  • 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_PR.AT-01

  • External link
  • Internal link

Resultaten 1 - 1 of 1

© 2024 redpencil.io. All rights reserved.