ISO 23234:2021 建物および土木工事—セキュリティ—構築環境におけるセキュリティ対策の計画 | ページ 6

3.1

security

state of relative freedom from threat (3.18) or harm caused by deliberate, unwanted, hostile or malicious acts

[SOURCE:ISO 19650-5:2020, 3.7]

3.2

protective security

use of measures when managing risk (3.20) linked to undesirable intentional actions

3.3

preventive security

planning, preparation, implementation and overseeing of protective security (3.2) measures which seek to eliminate or reduce risk (3.20) resulting from a threat (3.18)

3.4

actor

organization or individual that fulfils a role

3.5

project stage

delimited stage within a project

Note 1 to entry: A project stage can in turn be divided into sub-processes. The division is often justified on the basis of identifying deliverables, decisions, and changes of actors (3.4) . It can be adapted to the individual organization or situation.

3.6

strategic definition

project stage (3.5) during which the justification, overarching aim, and framework of the project are identified

3.7

preparation and brief

project stage (3.5) during which it is ascertained whether the project is feasible, and determined which conceptual solution is most appropriate

3.8

concept design

project stage (3.5) during which principles are developed for a technical solution with realistic strategies and plans for the project, so that a final decision on implementation can be made on a correct basis

3.9

developed design

project stage (3.5) that includes coordinated and updated proposals for structural design, building services systems, outline specifications, cost information and project strategies in accordance with the design programme

3.10

technical design

project stage (3.5) that occurs after the developed design (3.9) has been completed and in which the residual technical work of the core design team is completed

3.11

construction

project stage (3.5) during which deliverables are completed in accordance with plans and intentions

3.12

testing and handover

project stage (3.5) during which a fault-free technical delivery is handed over and it is ensured that all systems are correctly adjusted to their intended use

3.13

user

organization or person which uses or is intended to use, a building or other construction works

Note 1 to entry: A user can also be the owner of the building or construction works.

[SOURCE:ISO/TR 15686-11:2014, 3.1.131, modified —"animal or object" has been deleted; Note 1 to entry has been deleted and replaced with a new Note 1 to entry; cross-references to terminological entries in ISO 6707-1 have been removed.]

3.14

in use

project stage (3.5) during which technically sound and economic operation is ensured that satisfies the user's requirements for the project and that provides the intended effect

3.15

decommissioning

project stage (3.5) during which a viable and prudent conclusion to ownership or period of use is ensured

3.16

asset

item, thing or entity that has potential or actual value to an organization

Note 1 to entry: Value can be tangible or intangible, financial, or non-financial, and includes consideration of risks (3.20) and liabilities. It can be positive or negative at different stages of the asset life.

Note 2 to entry: Physical assets usually refer to equipment, inventory and properties owned by the organization. Physical assets are the opposite of intangible assets, which are non-physical assets such as leases, brands, digital assets, use rights, licences, intellectual property rights, reputation, or agreements.

Note 3 to entry: A grouping of assets referred to as an asset system could also be considered as an asset.

Note 4 to entry: Life, health and welfare of humans and other living beings can also be an asset.

Note 5 to entry: In the context of this document, organization can be understood as both owner and user of the physical asset in question.

[SOURCE:ISO 55000:2014, 3.2.1, modified — Notes 4 and 5 to entry have been added.]

3.17

vulnerability

lack of resilience against an undesirable intentional action or inability to recover a new stable condition of an asset (3.16)

3.18

threat

potential, deliberate action that can cause harm to an asset (3.16)

Note 1 to entry: A threat is always related to a threat actor (3.4) , which can be an individual or an organization.

3.19

design-basis threat

threat (3.18) used as a basis for preparing security measures

3.20

risk

effect of uncertainty on objectives

Note 1 to entry: An effect is a deviation from the expected. It can be positive, negative or both, and can address, create or result in opportunities and threats (3.18) .

Note 2 to entry: Objectives can have different aspects and categories, and can be applied at different levels.

Note 3 to entry: Risk is usually expressed in terms of risk sources, potential events, their consequences, and their likelihood.

Note 4 to entry: In the context of protective security (3.2) against threats, risk is usually expressed in terms of threat, impact, and vulnerability (3.17) .

Note 5 to entry: In the context of this document, risk is used as a negative deviation.

[SOURCE:ISO 31000:2018, 3.1, modified — Notes 4 and 5 to entry have been added.]

3.21

residual risk

risk (3.20) remaining after risk treatment

Note 1 to entry: Residual risk can contain unidentified risk.

Note 2 to entry: Residual risk can also be known as “retained risk”.

Note 3 to entry: “Risk treatment” in this document means carrying out mitigating measures to reduce the risk.

[SOURCE:ISO Guide 73:2009, 3.8.1.6, modified — Note 3 to entry has been added.]

3.22

risk assessment

overall process of risk (3.20) identification, risk analysis (3.23) and risk evaluation

[SOURCE:ISO Guide 73:2009, 3.4.1]

3.23

risk analysis

process to comprehend the nature of risk (3.20) and to determine the level of risk

Note 1 to entry: Risk analysis provides the basis for risk evaluation and decisions about risk treatment.

Note 2 to entry: Risk analysis includes risk estimation.

[SOURCE:ISO Guide 73:2009, 3.6.1]

3.24

stakeholder

person or organization that can affect, be affected by, or perceive themselves to be affected by a decision or activity

Note 1 to entry: A decision maker (3.25) can be a stakeholder.

[SOURCE:ISO Guide 73:2009, 3.2.1.1]

3.25

decision maker

top management or a person designated by the top management, and given delegated authority to make decisions

3.26

principal

person or organization that has initiated the project

Note 1 to entry: Principal can correspond to"developer" or"client".

3.27

project manager

person with the responsibility for planning, executing, and closing off a project

3.28

supplier

person or organization supplying materials or products

Note 1 to entry: In this document, supplier can also mean person or organization supplying services.

[SOURCE:ISO 6707-2:2017, 3.8.30, modified— Note 1 to entry has been added.]

3.29

security deliverable

security-specific written report, memorandum, drawing, digital information model, product solution or other documentable work based on specialist professional input

Note 1 to entry: The security deliverable is normally a sub-element of or input to the project to be executed.

3.30

external policy maker

external actor (3.4) that sets guidelines for the project and whom the project has little opportunity to influence

Note 1 to entry: External policy makers can include the police, planning and building authorities, heritage authorities, other public authorities, standards-setting bodies, etc.

3.31

security planner

adviser with knowledge and experience in managing the planning of the security works in construction projects with special security requirements

3.32

security risk adviser

adviser with knowledge and experience in undertaking risk assessments (3.22)

3.33

technical security adviser

adviser within a technical subject with special knowledge and experience in security (3.1) during the operational phase of the process

Note 1 to entry: This can include engineers with specialist knowledge and experience in the vulnerability (3.17) and security of structures, electro-technical installations, or other systems. This can also include architects or landscape architects with specialist knowledge and experience in security.

3.34

operational security adviser

adviser within the domain of human and organizational security measures during the operational phase of the project

Note 1 to entry: This role is often filled by the user's own security organization.