Concept skos:Concept Code ID.AM-02.3

The people responsible and accountable for managing software platforms and applications within the organisation shall be formally identified.

Also known as

skos:altLabel

Software management accountability

Note

skos:note

The goal of this control is to ensure that software platforms and applications are properly managed, by clearly identifying who is responsible for day-to-day operations and who is accountable for overall oversight and out- comes. To achieve this goal:

  • Define Roles Clearly Individuals responsible for managing software should be formally designated. These are the people who perform the work, make technical decisions, and carry out operational tasks (e.g. developers, system admin- istrators, testers).
  • Assign Accountability A separate role should be formally assigned to oversee and approve the successful completion of software- related tasks. This may include project managers, product owners, or team leads.
  • Apply to All Environments These roles should be defined for both IT and OT environments, ensuring that software used in industrial systems is also properly governed.

Place in the list

For people working with the data

Identifier (URI) http://cyfun.data.gift/data/requirement_ID_AM_02_3
All data (21 statements)

Properties and relations

Direct links from the subject.

Property Value

type

The subject is an instance of a class.

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

type

The subject is an instance of a class.

Concept

An idea or notion; a unit of thought.

label

A human-readable name for the subject.

ID.AM-02.3: The people responsible and accountable for managing software platforms and applications within the organisation shall be formally identified.

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

ID.AM-02.3

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_ESSENTIAL_E_p48

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

http://cyfun.data.gift/data/loc_CyFun2025_Booklet_IMPORTANT_E_p34

has broader

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

http://cyfun.data.gift/data/subcategory_ID.AM-02

note

A general note, for any purpose.

The goal of this control is to ensure that software platforms and applications are properly managed, by clearly identifying who is responsible for day-to-day operations and who is accountable for overall oversight and out- comes. To achieve this goal: - Define Roles Clearly Individuals responsible for managing software should be formally designated. These are the people who perform the work, make technical decisions, and carry out operational tasks (e.g. developers, system admin- istrators, testers). - Assign Accountability A separate role should be formally assigned to oversee and approve the successful completion of software- related tasks. This may include project managers, product owners, or team leads. - Apply to All Environments These roles should be defined for both IT and OT environments, ensuring that software used in industrial systems is also properly governed.

note

A general note, for any purpose.

The goal of this control is to ensure that software platforms and applications are properly managed, by clearly identifying who is responsible for day-to-day operations and who is accountable for overall oversight and out- comes. To achieve this goal: • Define Roles Clearly Individuals responsible for managing software should be formally designated. These are the people who perform the work, make technical decisions, and carry out operational tasks (e.g. developers, system admin- istrators, testers). • Assign Accountability A separate role should be formally assigned to oversee and approve the successful completion of software- related tasks. This may include project managers, product owners, or team leads. • Apply to All Environments These roles should be defined for both IT and OT environments, ensuring that software used in industrial systems is also properly governed.

note

A general note, for any purpose.

The goal of this control is to ensure that software platforms and applications are properly managed, by clearly identifying who is responsible for day-to-day operations and who is accountable for overall oversight and out- comes. To achieve this goal: - Define Roles Clearly Individuals responsible for managing software should be formally designated. These are the people who perform the work, make technical decisions, and carry out operational tasks (e.g. developers, system admin- istrators, testers). - Assign Accountability A separate role should be formally assigned to oversee and approve the successful completion of software- related tasks. This may include project managers, product owners, or team leads. - Apply to All Environments These roles should be defined for both IT and OT environments, ensuring that software used in industrial systems is also properly governed.

note

A general note, for any purpose.

<div><p>The goal of this control is to ensure that software platforms and applications are properly managed, by clearly identifying who is responsible for day-to-day operations and who is accountable for overall oversight and out- comes. To achieve this goal:</p><ul><li>Define Roles Clearly Individuals responsible for managing software should be formally designated. These are the people who perform the work, make technical decisions, and carry out operational tasks (e.g. developers, system admin- istrators, testers).</li><li>Assign Accountability A separate role should be formally assigned to oversee and approve the successful completion of software- related tasks. This may include project managers, product owners, or team leads.</li><li>Apply to All Environments These roles should be defined for both IT and OT environments, ensuring that software used in industrial systems is also properly governed.</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.

ID.AM-02.3

alternative label

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

Software management accountability

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.

The people responsible and accountable for managing software platforms and applications within the organisation shall be formally identified.

is in scheme

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

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

is in scheme

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

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

is in scheme

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

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

is in scheme

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

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

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

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

triple count

The number of triples associated with the subject.

19

in dataset

Specifies the dataset the subject is part of.

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

Resultaten 1 - 21 of 21

References

Inverse links to the subject.