diff --git a/process/folder_templates/modules/module_name/docs/index.rst b/process/folder_templates/modules/module_name/docs/index.rst index 026649f587..8e453d9bfb 100644 --- a/process/folder_templates/modules/module_name/docs/index.rst +++ b/process/folder_templates/modules/module_name/docs/index.rst @@ -21,5 +21,6 @@ Module Documents manual/index.rst safety_mgt/index.rst + security_mgt/index.rst verification/module_verification_report.rst release/release_note.rst diff --git a/process/folder_templates/modules/module_name/docs/manual/index.rst b/process/folder_templates/modules/module_name/docs/manual/index.rst index 08ba1a6e1a..df20dd55a3 100644 --- a/process/folder_templates/modules/module_name/docs/manual/index.rst +++ b/process/folder_templates/modules/module_name/docs/manual/index.rst @@ -19,3 +19,4 @@ Manuals :titlesonly: safety_manual + security_manual diff --git a/process/process_areas/security_management/guidance/security_management_security_manual_template.rst b/process/folder_templates/modules/module_name/docs/manual/security_manual.rst similarity index 87% rename from process/process_areas/security_management/guidance/security_management_security_manual_template.rst rename to process/folder_templates/modules/module_name/docs/manual/security_manual.rst index 2d40afc0ae..6bb8ec0929 100644 --- a/process/process_areas/security_management/guidance/security_management_security_manual_template.rst +++ b/process/folder_templates/modules/module_name/docs/manual/security_manual.rst @@ -12,18 +12,26 @@ # SPDX-License-Identifier: Apache-2.0 # ******************************************************************************* -Security Manual Template -========================= - -.. gd_temp:: Security Manual Template - :id: gd_temp__security_manual - :status: valid - :complies: - - Will be moved to Folder Templates (tbd https://github.com/eclipse-score/process_description/issues/109) - For the content see here: need:`doc__module_name_security_manual` - Will also adapted to the latest Safety ManualTemplate - +Module Security Manual +====================== + +.. note:: Document header + +.. document:: [Your Module Name] Security Manual + :id: doc__module_name_security_manual + :status: draft + :safety: ASIL_B + :security: YES + :realizes: wp__module_security_manual + :tags: template + +.. attention:: + The above directive must be updated according to your Module. + + - Modify ``Your Module Name`` to be your Module Name + - Modify ``id`` to be your Module Name in upper snake case preceded by ``doc__`` and succeeded by ``security_manual`` + - Adjust ``status`` to be ``valid`` + - Adjust ``security`` and ``tags`` according to your needs Introduction/Scope ------------------ diff --git a/process/folder_templates/modules/module_name/docs/security_mgt/index.rst b/process/folder_templates/modules/module_name/docs/security_mgt/index.rst new file mode 100644 index 0000000000..49998d3c7b --- /dev/null +++ b/process/folder_templates/modules/module_name/docs/security_mgt/index.rst @@ -0,0 +1,23 @@ +.. + # ******************************************************************************* + # Copyright (c) 2025 Contributors to the Eclipse Foundation + # + # See the NOTICE file(s) distributed with this work for additional + # information regarding copyright ownership. + # + # This program and the accompanying materials are made available under the + # terms of the Apache License Version 2.0 which is available at + # https://www.apache.org/licenses/LICENSE-2.0 + # + # SPDX-License-Identifier: Apache-2.0 + # ******************************************************************************* + +Security Management +################### + +.. toctree:: + :titlesonly: + + module_security_plan + module_security_plan_fdr + module_security_package_fdr diff --git a/process/process_areas/security_management/guidance/security_management_checklist_security_package.rst b/process/folder_templates/modules/module_name/docs/security_mgt/module_security_package_fdr.rst similarity index 75% rename from process/process_areas/security_management/guidance/security_management_checklist_security_package.rst rename to process/folder_templates/modules/module_name/docs/security_mgt/module_security_package_fdr.rst index 0b60ab029d..f666803d5a 100644 --- a/process/process_areas/security_management/guidance/security_management_checklist_security_package.rst +++ b/process/folder_templates/modules/module_name/docs/security_mgt/module_security_package_fdr.rst @@ -12,13 +12,27 @@ # SPDX-License-Identifier: Apache-2.0 # ******************************************************************************* -Security Package Formal Review Checklist -======================================== +Security Package Formal Review Report +===================================== + +.. note:: Document header + +.. document:: [Your Module Name] Security Package Formal Review + :id: doc__module_name_security_package_fdr + :status: draft + :safety: ASIL_B + :security: YES + :realizes: wp__fdr_reports + :tags: template + +.. attention:: + The above directive must be updated according to your Module. + + - Modify ``Your Module Name`` to be your Module Name + - Modify ``id`` to be your Module Name in upper snake case preceded by ``doc_`` and succeeded by ``safety_package_fdr`` + - Adjust ``status`` to be ``valid`` + - Adjust ``safety`` and ``tags`` according to your needs -.. gd_chklst:: Security Package Formal Review Checklist - :id: gd_chklst__security_package - :status: valid - :complies: std_req__isosae21434__prj_management_6471, std_req__isosae21434__prj_management_6491, std_req__isosae21434__prj_management_6492 **1. Purpose** diff --git a/process/process_areas/security_management/guidance/security_management_module_security_plan_template.rst b/process/folder_templates/modules/module_name/docs/security_mgt/module_security_plan.rst similarity index 89% rename from process/process_areas/security_management/guidance/security_management_module_security_plan_template.rst rename to process/folder_templates/modules/module_name/docs/security_mgt/module_security_plan.rst index 6a93f8594d..b736e59c73 100644 --- a/process/process_areas/security_management/guidance/security_management_module_security_plan_template.rst +++ b/process/folder_templates/modules/module_name/docs/security_mgt/module_security_plan.rst @@ -12,18 +12,26 @@ # SPDX-License-Identifier: Apache-2.0 # ******************************************************************************* -Module Security Plan Template -============================= +Module Security Plan +==================== -.. gd_temp:: Module Security Plan Template - :id: gd_temp__module_security_plan - :status: valid - :complies: +.. note:: Document header - Will be moved to Folder Templates (tbd https://github.com/eclipse-score/process_description/issues/109) - For the content see here: need:`doc__module_name_security_plan` - Will also adapted to the latest Safety Plan Template +.. document:: [Your Module Name] Security Plan + :id: doc__module_name_security_plan + :status: draft + :safety: ASIL_B + :security: YES + :realizes: wp__module_security_plan + :tags: template +.. attention:: + The above directive must be updated according to your Module. + + - Modify ``Your Module Name`` to be your Module Name + - Modify ``id`` to be your Module Name in upper snake case preceded by ``doc_`` and succeeded by ``security_plan`` + - Adjust ``status`` to be ``valid`` + - Adjust ``safety`` and ``tags`` according to your needs | **1. Security Management Context** @@ -75,14 +83,14 @@ Module Security Plan Template - * - :need:`wp__fdr_reports` (module Security Plan) - - :need:`gd_chklst__security_plan` + - :need:`gd_chklst__module_security_plan` - - - - * - :need:`wp__fdr_reports` (module Security Package) - - :need:`Security Package Formal Review Checklist ` + - :need:`Security Package Formal Review Checklist ` - - - @@ -110,7 +118,7 @@ Module Security Plan Template - * - :need:`wp__module_security_manual` - - :need:`gd_temp__security_manual` + - :need:`gd_temp__module_security_manual` - - - diff --git a/process/process_areas/security_management/guidance/security_management_checklist_security_plan.rst b/process/folder_templates/modules/module_name/docs/security_mgt/module_security_plan_fdr.rst similarity index 73% rename from process/process_areas/security_management/guidance/security_management_checklist_security_plan.rst rename to process/folder_templates/modules/module_name/docs/security_mgt/module_security_plan_fdr.rst index 623b1d4fea..8e4509456a 100644 --- a/process/process_areas/security_management/guidance/security_management_checklist_security_plan.rst +++ b/process/folder_templates/modules/module_name/docs/security_mgt/module_security_plan_fdr.rst @@ -12,17 +12,31 @@ # SPDX-License-Identifier: Apache-2.0 # ******************************************************************************* -Security Plan Review Checklist -============================== +Module Security Plan Formal Review Report +========================================= -.. gd_chklst:: Security Plan Review Checklist - :id: gd_chklst__security_plan - :status: valid - :complies: std_req__isosae21434__prj_management_6411, std_req__isosae21434__prj_management_6421, std_req__isosae21434__prj_management_6422, std_req__isosae21434__prj_management_6423, std_req__isosae21434__prj_management_6424, std_req__isosae21434__prj_management_6425, std_req__isosae21434__prj_management_6426, std_req__isosae21434__prj_management_6427, std_req__isosae21434__prj_management_6428, std_req__isosae21434__prj_management_6429, std_req__isosae21434__prj_management_64210, std_req__isosae21434__prj_management_64211, std_req__isosae21434__prj_management_6431, std_req__isosae21434__prj_management_6432, std_req__isosae21434__prj_management_6441, std_req__isosae21434__prj_management_6442, std_req__isosae21434__prj_management_6443, std_req__isosae21434__prj_management_6451, std_req__isosae21434__prj_management_6452, std_req__isosae21434__prj_management_6453, std_req__isosae21434__prj_management_6461, std_req__isosae21434__prj_management_6462 +.. note:: Document header + +.. document:: [Your Module Name] Security Plan Formal Review + :id: doc__module_name_security_plan_fdr + :status: draft + :safety: ASIL_B + :security: YES + :realizes: wp__fdr_reports + :tags: template + +.. attention:: + The above directive must be updated according to your Module. + + - Modify ``Your Module Name`` to be your Module Name + - Modify ``id`` to be your Module Name in upper snake case preceded by ``doc_`` and succeeded by ``_security_plan_fdr`` + - Adjust ``status`` to be ``valid`` + - Adjust ``safety`` and ``tags`` according to your needs **1. Purpose** -The purpose of this security plan review checklist is to report status of the review for the security plan. +The purpose of this review checklist is to provide a guidence for reviewing the security plans for each module. +Each module security plan shall one checklist filled. **2. Checklist** diff --git a/process/folder_templates/platform/index.rst b/process/folder_templates/platform/index.rst index 721fb404de..ea78b48533 100644 --- a/process/folder_templates/platform/index.rst +++ b/process/folder_templates/platform/index.rst @@ -22,5 +22,10 @@ Platform safety_analysis/platform_dfa.rst requirements/stakeholder/chklst_req_inspection.rst - safety_planning/index.rst + safety_planning/platform_safety_plan.rst safety_planning/platform_safety_analysis_fdr.rst + security_analysis/platform_security_manual.rst + security_analysis/platform_security_analysis_fdr.rst + security_analysis/platform_security_package_fdr.rst + security_planning/platform_security_plan.rst + security_planning/platform_security_plan_fdr.rst diff --git a/process/folder_templates/platform/safety_planning/index.rst b/process/folder_templates/platform/safety_planning/platform_safety_plan.rst similarity index 100% rename from process/folder_templates/platform/safety_planning/index.rst rename to process/folder_templates/platform/safety_planning/platform_safety_plan.rst diff --git a/process/folder_templates/platform/security_analysis/platform_security_analysis_fdr.rst b/process/folder_templates/platform/security_analysis/platform_security_analysis_fdr.rst new file mode 100644 index 0000000000..fc454088f8 --- /dev/null +++ b/process/folder_templates/platform/security_analysis/platform_security_analysis_fdr.rst @@ -0,0 +1,41 @@ +.. + # ******************************************************************************* + # Copyright (c) 2025 Contributors to the Eclipse Foundation + # + # See the NOTICE file(s) distributed with this work for additional + # information regarding copyright ownership. + # + # This program and the accompanying materials are made available under the + # terms of the Apache License Version 2.0 which is available at + # https://www.apache.org/licenses/LICENSE-2.0 + # + # SPDX-License-Identifier: Apache-2.0 + # ******************************************************************************* + + +Security Analysis Checklist +=========================== + +.. document:: [Your Platform Name] Security Analysis Checklist + :id: doc__platform_name_security_analysis_fdr + :status: draft + :safety: ASIL_B + :security: YES + :realizes: wp__fdr_reports + :tags: template + +.. attention:: + The above directive must be updated according to your Platform. + + - Modify ``Your Platform Name`` to be your Platform Name + - Modify ``id`` to be your Platform Name in lower snake case preceded by ``doc__`` and followed by ``_security_analysis_fdr`` + - Adjust ``status`` to be ``valid`` + - Adjust ``safety``, ``security`` and ``tags`` according to your needs + + +**Purpose** +The purpose of this Security Analysis checklist template is to collect the topics to be checked during verification of the Security Analysis. + +**Checklist** + +To be filled as part of https://github.com/eclipse-score/process_description/issues/452. diff --git a/process/folder_templates/platform/security_analysis/platform_security_manual.rst b/process/folder_templates/platform/security_analysis/platform_security_manual.rst new file mode 100644 index 0000000000..32e4bf500f --- /dev/null +++ b/process/folder_templates/platform/security_analysis/platform_security_manual.rst @@ -0,0 +1,92 @@ +.. + # ******************************************************************************* + # Copyright (c) 2025 Contributors to the Eclipse Foundation + # + # See the NOTICE file(s) distributed with this work for additional + # information regarding copyright ownership. + # + # This program and the accompanying materials are made available under the + # terms of the Apache License Version 2.0 which is available at + # https://www.apache.org/licenses/LICENSE-2.0 + # + # SPDX-License-Identifier: Apache-2.0 + # ******************************************************************************* + +Platform Security Manual +======================== + +.. note:: Document header + +.. document:: Platform Security Manual + :id: doc__platform_security_manual + :status: draft + :safety: ASIL_B + :security: YES + :realizes: wp__platform_security_manual + :tags: template + +Introduction/Scope +------------------ +.. note:: The platform Security Manual is only performed once at platform level to analyse the dependencies between the features of the platform. + The results shall be used as an input for the safety analysis so that general safety mechanisms are only defined once and not in every single safety analysis. + +Assumed Platform Security Requirements +-------------------------------------- +| For the the following security related stakeholder requirements are assumed to define the top level functionality (purpose) of the . i.e. from these all the feature and component requirements implemented are derived. +| + +Assumptions of Use +------------------ + +Assumptions on the Environment +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +| Generally the assumption of the Project platform OoC is that it is integrated in a secure system, i.e. the POSIX OS it runs on is qualified and also the HW related failures are taken into account by the system integrator, if not otherwise stated in the module's security concept. +| + +List of AoUs expected from the environment the platform / module runs on: + +.. needtable:: + :style: table + :columns: title;id;status + :colwidths: 25,25,25 + :sort: title + + results = [] + + for need in needs.filter_types(["aou_req"]): + if need and "environment" in need["tags"]: + results.append(need) + +Assumptions on the User +^^^^^^^^^^^^^^^^^^^^^^^ +| As there is no assumption on which specific OS and HW is used, the integration testing of the stakeholder and feature requirements is expected to be performed by the user of the platform EooC. Tests covering all stakeholder and feature requirements performed on a reference platform (tbd link to reference platform specification), reviewed and passed are included in the platform EooC security package. +| Additionally the components of the platform may have additional specific assumptions how they are used. These are part of every module documentation: . Assumptions from components to their users can be fulfilled in two ways: +| 1. There are assumption which need to be fulfilled by all SW components, e.g. "every user of an IPC mechanism needs to make sure that he provides correct data (e.g. including appropriate security (access) control)" - in this case the AoU is marked as "platform". +| 2. There are assumption which can be fulfilled by a security control realized by some other Project platform component and are therefore not relevant for an user who uses the whole platform. But those are relevant if you chose to use the module EooC stand-alone - in this case the AoU is marked as "module". An example would be the "JSON read" which requires "The user shall provide a string as input which is not corrupted due to HW or QM SW errors." - which is covered when using together with safe platform persistency feature. + +List of AoUs on the user of the platform features or the module of this security manual: + +.. needtable:: + :style: table + :columns: title;id;status + :colwidths: 25,25,25 + :sort: title + + results = [] + + for need in needs.filter_types(["aou_req"]): + if need and "environment" not in need["tags"]: + results.append(need) + +Security concept of the OoC +---------------------------- +| + +Security Weaknesses, Vulnerabilities +------------------------------------ +| Weaknesses, Vulnerabilities (bugs in security relevant SW, detected by testing or by users, which could not be fixed) known before release are documented in the platform/module release notes . + +References +---------- +| +| diff --git a/process/folder_templates/platform/security_analysis/platform_security_package_fdr.rst b/process/folder_templates/platform/security_analysis/platform_security_package_fdr.rst new file mode 100644 index 0000000000..c16152ab52 --- /dev/null +++ b/process/folder_templates/platform/security_analysis/platform_security_package_fdr.rst @@ -0,0 +1,42 @@ +.. + # ******************************************************************************* + # Copyright (c) 2025 Contributors to the Eclipse Foundation + # + # See the NOTICE file(s) distributed with this work for additional + # information regarding copyright ownership. + # + # This program and the accompanying materials are made available under the + # terms of the Apache License Version 2.0 which is available at + # https://www.apache.org/licenses/LICENSE-2.0 + # + # SPDX-License-Identifier: Apache-2.0 + # ******************************************************************************* + + +Platform Security Package Checklist +=================================== + +.. document:: [Your Platform Name] Security Package Checklist + :id: doc__platform_name_security_package_fdr + :status: draft + :safety: ASIL_B + :security: YES + :realizes: wp__fdr_reports + :tags: template + +.. attention:: + The above directive must be updated according to your Platform. + + - Modify ``Your Platform Name`` to be your Platform Name + - Modify ``id`` to be your Platform Name in lower snake case preceded by ``doc__`` and followed by ``_security_package_fdr`` + - Adjust ``status`` to be ``valid`` + - Adjust ``safety``, ``security`` and ``tags`` according to your needs + + +**Purpose** +The purpose of this Platform Security package checklist template is to collect the topics to be checked during verification of the Platform Security package. + +**Checklist** +.. Question: Create a task for this. + +To be filled. diff --git a/process/folder_templates/platform/security_planning/platform_security_plan.rst b/process/folder_templates/platform/security_planning/platform_security_plan.rst new file mode 100644 index 0000000000..3a4b27863d --- /dev/null +++ b/process/folder_templates/platform/security_planning/platform_security_plan.rst @@ -0,0 +1,160 @@ +.. + # ******************************************************************************* + # Copyright (c) 2025 Contributors to the Eclipse Foundation + # + # See the NOTICE file(s) distributed with this work for additional + # information regarding copyright ownership. + # + # This program and the accompanying materials are made available under the + # terms of the Apache License Version 2.0 which is available at + # https://www.apache.org/licenses/LICENSE-2.0 + # + # SPDX-License-Identifier: Apache-2.0 + # ******************************************************************************* + +.. _platform_security_plan_template: + +Security Planning +################# + +.. document:: Platform Security Plan + :id: doc__platform_security_plan + :status: draft + :safety: ASIL_B + :security: YES + :realizes: wp__platform_security_plan + :tags: template + +.. attention:: + The above directive must be updated according to your Platform. + + - Adjust ``status`` to be ``valid`` + - Adjust ``safety``, ``security`` and ``tags`` according to your needs + + +:note: The Security Management Plan shall be continuously maintained during the project. Deviations to the platform plan should be documented here. + + +Security management / Platform Security Plan +-------------------------------------------- + +Purpose ++++++++ + +Description of the purpose of the Security Management Plan. + +Objectives and Scope +++++++++++++++++++++ + +Security Management Goals +^^^^^^^^^^^^^^^^^^^^^^^^^ + +Description of the Security Management goals. + +Security Management Scope +^^^^^^^^^^^^^^^^^^^^^^^^^ + +Description of the Security Management scope. + +Tailoring +^^^^^^^^^ + +Description of the tailoring of security activities in the project. + +Approach +++++++++ + +Security Culture +^^^^^^^^^^^^^^^^ + +Description of the security culture in the project. + +Security Management Organization +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +Description of the organization of the Security Management in the project. + +*Eclipse Roles* + +Description of the Eclipse foundation roles relevant for Security Management. + +*Project Roles* + +Description of the project roles relevant for Security Management. + +*Critical dependencies* + +Description of critical dependencies relevant for Security Management. + +*Risk* + +Description of risks relevant for Security Management. + +*Skills* + +Description of skills relevant for Security Management. + +Security Resources +^^^^^^^^^^^^^^^^^^ + +Description of the resources relevant for Security Management. + +Security Management Communication +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +Description of the communication relevant for Security Management. + +*Reporting* + +Description of reporting used for Security Management. + +*Escalation* + +Description of escalation path used for Security Management. + +Security Management Life Cycle +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +Description of the Security management life cycle. + +Security Requirements +^^^^^^^^^^^^^^^^^^^^^ + +Description of Security requirements. + +Security Schedule +^^^^^^^^^^^^^^^^^ +Description of the Security schedule. + +Security SW Development +^^^^^^^^^^^^^^^^^^^^^^^ +Description of the Security development. + +Security Verification +^^^^^^^^^^^^^^^^^^^^^ +Description of the Security verification. + +Security Tool Management +^^^^^^^^^^^^^^^^^^^^^^^^ +Description of the Security tool management. + +Security Work Products +^^^^^^^^^^^^^^^^^^^^^^ +Description of the Security work products. + +Security Quality Criteria +^^^^^^^^^^^^^^^^^^^^^^^^^ +Description of the Security quality criteria. + +Platform Security Plan +++++++++++++++++++++++ + +Security Specific SW Platform Work Products +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +List of all relevant Security Management work products for the platform project. + +Security Management Feature Specific Work Products +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +List of all relevant Security Management work products at feature level. diff --git a/process/folder_templates/platform/security_planning/platform_security_plan_fdr.rst b/process/folder_templates/platform/security_planning/platform_security_plan_fdr.rst new file mode 100644 index 0000000000..a9d9eada20 --- /dev/null +++ b/process/folder_templates/platform/security_planning/platform_security_plan_fdr.rst @@ -0,0 +1,41 @@ +.. + # ******************************************************************************* + # Copyright (c) 2025 Contributors to the Eclipse Foundation + # + # See the NOTICE file(s) distributed with this work for additional + # information regarding copyright ownership. + # + # This program and the accompanying materials are made available under the + # terms of the Apache License Version 2.0 which is available at + # https://www.apache.org/licenses/LICENSE-2.0 + # + # SPDX-License-Identifier: Apache-2.0 + # ******************************************************************************* + + +Platform Security Plan Formal Review Report +=========================================== + +.. document:: [Your Platform Name] Security Analysis Checklist + :id: doc__platform_name_security_plan_fdr + :status: draft + :safety: ASIL_B + :security: YES + :realizes: wp__fdr_reports + :tags: template + +.. attention:: + The above directive must be updated according to your Platform. + + - Modify ``Your Platform Name`` to be your Platform Name + - Modify ``id`` to be your Platform Name in lower snake case preceded by ``doc__`` and followed by ``_security_plan_fdr`` + - Adjust ``status`` to be ``valid`` + - Adjust ``safety`` and ``tags`` according to your needs + + +**Purpose** +The purpose of this Security Plan checklist template is to collect the topics to be checked during verification of the Platform Security Plan. + +**Checklist** + +Further details to be filled during https://github.com/eclipse-score/process_description/issues/452 diff --git a/process/process_areas/quality_management/guidance/quality_review_checklist.rst b/process/process_areas/quality_management/guidance/quality_review_checklist.rst index 6fd1d6c8d5..360c88d98e 100644 --- a/process/process_areas/quality_management/guidance/quality_review_checklist.rst +++ b/process/process_areas/quality_management/guidance/quality_review_checklist.rst @@ -173,7 +173,7 @@ Security Management plan review checklist template * - Review Id - Link to checklist * - SecMP_00_01 - - :need:`gd_chklst__security_plan` + - :need:`gd_chklst__module_security_plan` Quality Management plan review checklist template diff --git a/process/process_areas/safety_management/safety_management_concept.rst b/process/process_areas/safety_management/safety_management_concept.rst index 6de327cf19..534300500f 100644 --- a/process/process_areas/safety_management/safety_management_concept.rst +++ b/process/process_areas/safety_management/safety_management_concept.rst @@ -72,6 +72,10 @@ Stakeholders * Performing safety related development * Create Component Classification +#. :need:`Security Manager ` + + * Supports activities + #. :need:`External Auditor ` * Perform Safety Audit as independent safety audits @@ -99,6 +103,6 @@ Safety Management Tooling For the safety planning and safety manual a “Docs-as-Code” approach is used and within that approach Id will be used for referencing. -For the activities planning (who, when) we use a Issue Tracking System to create and manage issues, and monitor progress through a project management dashboard. +For the activities planning (who, when) we use :need:`wp__issue_track_system` to create and manage issues, and monitor progress through a project management dashboard. For the reporting (e.g. displaying the status of the work products) additional tooling is created. diff --git a/process/process_areas/safety_management/safety_management_roles.rst b/process/process_areas/safety_management/safety_management_roles.rst index c8768d6d5a..988cd1450c 100644 --- a/process/process_areas/safety_management/safety_management_roles.rst +++ b/process/process_areas/safety_management/safety_management_roles.rst @@ -69,7 +69,6 @@ Roles * Refusing the approval of work products as defined in the workflows * Refusing the approval of his team's role nomination (i.e. requesting that the role will be withdrawn) - .. role:: External Auditor :id: rl__external_auditor :status: valid diff --git a/process/process_areas/safety_management/safety_management_workflow.rst b/process/process_areas/safety_management/safety_management_workflow.rst index 54714e65fe..0fac6ae24a 100644 --- a/process/process_areas/safety_management/safety_management_workflow.rst +++ b/process/process_areas/safety_management/safety_management_workflow.rst @@ -125,7 +125,7 @@ Safety Management Workflows :input: wp__platform_mgmt, wp__issue_track_system, wp__sw_component_class, wp__safety_tailoring :output: wp__issue_track_system :contains: gd_temp__change_component_request, gd_temp__change_decision_record, gd_temp__change_impact_analysis - :has: doc_concept__safety_management_process + :has: doc_concept__safety_management_process, doc_getstrt__safety_management_process | In accordance with ISO 26262-2:2018 section 5.2.2.3 d/e (Impact Analysis), the project implements a dedicated workflow for analyzing change requests. | The Safety Manager is responsible for ensuring that each change request is analyzed for its impact on safety, as required by ISO 26262-2:2018. diff --git a/process/process_areas/security_management/guidance/checklist_security_package.rst b/process/process_areas/security_management/guidance/checklist_security_package.rst new file mode 100644 index 0000000000..ecc402a691 --- /dev/null +++ b/process/process_areas/security_management/guidance/checklist_security_package.rst @@ -0,0 +1,30 @@ +.. + # ******************************************************************************* + # Copyright (c) 2025 Contributors to the Eclipse Foundation + # + # See the NOTICE file(s) distributed with this work for additional + # information regarding copyright ownership. + # + # This program and the accompanying materials are made available under the + # terms of the Apache License Version 2.0 which is available at + # https://www.apache.org/licenses/LICENSE-2.0 + # + # SPDX-License-Identifier: Apache-2.0 + # ******************************************************************************* + +Security Package Formal Review Checklist +======================================== + +.. gd_chklst:: Platform Security Package Formal Review Checklist + :id: gd_chklst__platform_security_package + :status: valid + :complies: std_req__isosae21434__prj_management_6471, std_req__isosae21434__prj_management_6491, std_req__isosae21434__prj_management_6492 + + For the content see here: :need:`doc__platform_name_security_package_fdr` + +.. gd_chklst:: Module Security Package Formal Review Checklist + :id: gd_chklst__module_security_package + :status: valid + :complies: std_req__isosae21434__prj_management_6471, std_req__isosae21434__prj_management_6491, std_req__isosae21434__prj_management_6492 + + For the content see here: :need:`doc__module_name_security_package_fdr` diff --git a/process/process_areas/security_management/guidance/checklist_security_plan.rst b/process/process_areas/security_management/guidance/checklist_security_plan.rst new file mode 100644 index 0000000000..05192807bf --- /dev/null +++ b/process/process_areas/security_management/guidance/checklist_security_plan.rst @@ -0,0 +1,30 @@ +.. + # ******************************************************************************* + # Copyright (c) 2025 Contributors to the Eclipse Foundation + # + # See the NOTICE file(s) distributed with this work for additional + # information regarding copyright ownership. + # + # This program and the accompanying materials are made available under the + # terms of the Apache License Version 2.0 which is available at + # https://www.apache.org/licenses/LICENSE-2.0 + # + # SPDX-License-Identifier: Apache-2.0 + # ******************************************************************************* + +Security Plan Formal Review Checklist +===================================== + +.. gd_chklst:: Platform Security Plan Formal Review Checklist + :id: gd_chklst__platform_security_plan + :status: valid + :complies: std_req__isosae21434__prj_management_6411, std_req__isosae21434__prj_management_6421, std_req__isosae21434__prj_management_6422, std_req__isosae21434__prj_management_6423, std_req__isosae21434__prj_management_6424, std_req__isosae21434__prj_management_6425, std_req__isosae21434__prj_management_6426, std_req__isosae21434__prj_management_6427, std_req__isosae21434__prj_management_6428, std_req__isosae21434__prj_management_6429, std_req__isosae21434__prj_management_64210, std_req__isosae21434__prj_management_64211, std_req__isosae21434__prj_management_6431, std_req__isosae21434__prj_management_6432, std_req__isosae21434__prj_management_6441, std_req__isosae21434__prj_management_6442, std_req__isosae21434__prj_management_6443, std_req__isosae21434__prj_management_6451, std_req__isosae21434__prj_management_6452, std_req__isosae21434__prj_management_6453, std_req__isosae21434__prj_management_6461, std_req__isosae21434__prj_management_6462 + + For the content see here: :need:`doc__platform_name_security_plan_fdr` + +.. gd_chklst:: Module Security Plan Formal Review Checklist + :id: gd_chklst__module_security_plan + :status: valid + :complies: std_req__isosae21434__prj_management_6411, std_req__isosae21434__prj_management_6421, std_req__isosae21434__prj_management_6422, std_req__isosae21434__prj_management_6423, std_req__isosae21434__prj_management_6424, std_req__isosae21434__prj_management_6425, std_req__isosae21434__prj_management_6426, std_req__isosae21434__prj_management_6427, std_req__isosae21434__prj_management_6428, std_req__isosae21434__prj_management_6429, std_req__isosae21434__prj_management_64210, std_req__isosae21434__prj_management_64211, std_req__isosae21434__prj_management_6431, std_req__isosae21434__prj_management_6432, std_req__isosae21434__prj_management_6441, std_req__isosae21434__prj_management_6442, std_req__isosae21434__prj_management_6443, std_req__isosae21434__prj_management_6451, std_req__isosae21434__prj_management_6452, std_req__isosae21434__prj_management_6453, std_req__isosae21434__prj_management_6461, std_req__isosae21434__prj_management_6462 + + For the content see here: :need:`doc__module_name_security_plan_fdr` diff --git a/process/process_areas/security_management/guidance/index.rst b/process/process_areas/security_management/guidance/index.rst index 1ac3787c36..16f720ff5b 100644 --- a/process/process_areas/security_management/guidance/index.rst +++ b/process/process_areas/security_management/guidance/index.rst @@ -19,9 +19,9 @@ Guidance :maxdepth: 1 security_management_guideline + security_plan_templates + security_manual_templates security_management_feature_security_wp_template - security_management_module_security_plan_template - security_management_security_manual_template - security_management_checklist_security_package - security_management_checklist_security_plan + checklist_security_package + checklist_security_plan security_management_process_reqs diff --git a/process/process_areas/security_management/guidance/security_management_feature_security_wp_template.rst b/process/process_areas/security_management/guidance/security_management_feature_security_wp_template.rst index e54241d008..66984ec504 100644 --- a/process/process_areas/security_management/guidance/security_management_feature_security_wp_template.rst +++ b/process/process_areas/security_management/guidance/security_management_feature_security_wp_template.rst @@ -12,6 +12,8 @@ # SPDX-License-Identifier: Apache-2.0 # ******************************************************************************* +.. It is still unclear if Security analysis at Feature level is needed or not (and how will it be different when compared to Module level analysis?). This checklit is kept as it is for now. but it will be more clear when we actually pilot one. + Feature Security Work Products Template ======================================= diff --git a/process/process_areas/security_management/guidance/security_management_guideline.rst b/process/process_areas/security_management/guidance/security_management_guideline.rst index 82564beb67..5292f2ac24 100644 --- a/process/process_areas/security_management/guidance/security_management_guideline.rst +++ b/process/process_areas/security_management/guidance/security_management_guideline.rst @@ -23,9 +23,7 @@ Security Management Guideline :complies: std_req__isosae21434__org_management_5421, std_req__isosae21434__org_management_5422, std_req__isosae21434__org_management_5423, std_req__isosae21434__org_management_5443, std_req__isosae21434__org_management_5451, std_req__isosae21434__org_management_5461, std_req__isosae21434__continual_8321, std_req__isosae21434__continual_8322, std_req__aspice_40__iic-14-55 - **Overall security management:** - - Security culture: + **Security culture:** Security culture is planned to grow in the SW platform. This shall be fostered by doing a lessons learned after each feature development completion, @@ -36,12 +34,12 @@ Security Management Guideline are defined with experience of several companies already performing successful safe and secure SW development. This also improves independence of reviews for the process definitions. - Quality Management: + **Quality Management:** ASPICE standard is selected for quality management. Processes will always link to the :ref:`standard_isosae21434` standard and to the :ref:`standard_aspice_pam4` standard. - Competence management: + **Competence management:** The :need:`rl__security_manager` on SW platform level is responsible to define a competence management for the whole platform. Expectation is that the security competence of the persons @@ -50,14 +48,14 @@ Security Management Guideline So the module security managers shall consult the :need:`wp__platform_security_plan` and perform accordingly in their module project. - Communication: + **Communication:** Development teams are interdisciplinary, so the regular (sprint) planning and review meetings enable communication (as defined in :need:`wp__platform_mgmt`). Another main communication means are the Pull Request reviews. Also the standard Eclipse Foundation communication strategies are used (e.g. mailing lists) - Security Weaknesses, Vulnerabilities: + **Security Weaknesses, Vulnerabilities:** As the SW platform organization does not have own vehicles in the field, it relies on feedback from OEMs and Distributors on bugs discovered in the field. The need for this feedback is part @@ -72,7 +70,7 @@ Security Management Guideline via the :need:`wp__issue_track_system` (which is also Open Source). - **Tailoring security activities:** + **Tailoring Security activities:** Main tailoring driver is that the SW platform is pure SW development and is provided as "(component) OoC" - this explains mainly the generic, platform wide tailoring. @@ -83,7 +81,7 @@ Security Management Guideline existing components is the main tailoring driver. - **Planning security activities:** + **Planning Security activities:** In the security plan the nomination of the security manager and the project lead is documented. The planning of security activities is done using issues in the :need:`wp__issue_track_system` @@ -140,6 +138,7 @@ Security Management Guideline See the respective work products: + * platform level: :need:`wp__platform_security_analysis` * feature level: :need:`wp__feature_security_analysis` * component level: :need:`wp__sw_component_security_analysis` @@ -178,7 +177,7 @@ Security Management Guideline instruct the user of a OoC (in this project on platform and module level) to securely use it in the context of the user's OoC and requirements for post-development. Its main content is described in :need:`wp__platform_security_manual` and :need:`wp__module_security_manual`. - A template exists to guide the definition of the security manual on platform and module level (:need:`gd_temp__security_manual`). + A template exists to guide the definition of the security manual on platform and module level (:need:`doc__module_name_security_manual`). .. gd_guidl:: Security package automated generation :id: gd_guidl__security_package diff --git a/process/process_areas/security_management/guidance/security_management_process_reqs.rst b/process/process_areas/security_management/guidance/security_management_process_reqs.rst index fbabb9a504..89153476a7 100644 --- a/process/process_areas/security_management/guidance/security_management_process_reqs.rst +++ b/process/process_areas/security_management/guidance/security_management_process_reqs.rst @@ -21,7 +21,7 @@ Security Management Process Requirements :status: valid :tags: done_automation, attribute, mandatory :satisfies: wf__cr_mt_security_plan - :complies: + :complies: std_req__isosae21434__prj_management_6429 Security plans shall contain documents references where the status is derived automatically. @@ -32,7 +32,7 @@ Security Management Process Requirements :status: valid :tags: prio_2_automation, attribute, mandatory :satisfies: wf__cr_mt_security_plan - :complies: + :complies: std_req__isosae21434__prj_management_6429 Security plans shall contain work product references where the accumulated status is derived automatically. diff --git a/process/process_areas/security_management/guidance/security_manual_templates.rst b/process/process_areas/security_management/guidance/security_manual_templates.rst new file mode 100644 index 0000000000..ee2ddc8264 --- /dev/null +++ b/process/process_areas/security_management/guidance/security_manual_templates.rst @@ -0,0 +1,29 @@ +.. + # ******************************************************************************* + # Copyright (c) 2025 Contributors to the Eclipse Foundation + # + # See the NOTICE file(s) distributed with this work for additional + # information regarding copyright ownership. + # + # This program and the accompanying materials are made available under the + # terms of the Apache License Version 2.0 which is available at + # https://www.apache.org/licenses/LICENSE-2.0 + # + # SPDX-License-Identifier: Apache-2.0 + # ******************************************************************************* + +Security Manual Templates +========================= +.. gd_temp:: Platform Security Manual Template + :id: gd_temp__platform_security_manual + :status: valid + :complies: std_req__isosae21434__development_10421, std_req__isosae21434__development_10422 + + For the content see here: :need:`doc__platform_security_manual` + +.. gd_temp:: Module Security Manual Template + :id: gd_temp__module_security_manual + :status: valid + :complies: std_req__isosae21434__development_10421, std_req__isosae21434__development_10422 + + For the content see here: :need:`doc__module_name_security_manual` diff --git a/process/process_areas/security_management/guidance/security_plan_templates.rst b/process/process_areas/security_management/guidance/security_plan_templates.rst new file mode 100644 index 0000000000..64a161ba09 --- /dev/null +++ b/process/process_areas/security_management/guidance/security_plan_templates.rst @@ -0,0 +1,30 @@ +.. + # ******************************************************************************* + # Copyright (c) 2025 Contributors to the Eclipse Foundation + # + # See the NOTICE file(s) distributed with this work for additional + # information regarding copyright ownership. + # + # This program and the accompanying materials are made available under the + # terms of the Apache License Version 2.0 which is available at + # https://www.apache.org/licenses/LICENSE-2.0 + # + # SPDX-License-Identifier: Apache-2.0 + # ******************************************************************************* + +Security Planning Templates +=========================== + +.. gd_temp:: Platform Security Plan Template + :id: gd_temp__platform_security_plan + :status: valid + :complies: std_req__isosae21434__prj_management_6411, std_req__isosae21434__prj_management_6421, std_req__isosae21434__prj_management_6422, std_req__isosae21434__prj_management_6423, std_req__isosae21434__prj_management_6424, std_req__isosae21434__prj_management_6425, std_req__isosae21434__prj_management_6426, std_req__isosae21434__prj_management_6427, std_req__isosae21434__prj_management_6428, std_req__isosae21434__prj_management_6429, std_req__isosae21434__prj_management_64210, std_req__isosae21434__prj_management_64211, std_req__isosae21434__prj_management_6431, std_req__isosae21434__prj_management_6432, std_req__isosae21434__prj_management_6441, std_req__isosae21434__prj_management_6442, std_req__isosae21434__prj_management_6443, std_req__isosae21434__prj_management_6451, std_req__isosae21434__prj_management_6452, std_req__isosae21434__prj_management_6453, std_req__isosae21434__prj_management_6461, std_req__isosae21434__prj_management_6462 + + For the content see here: :need:`doc__platform_security_plan` + +.. gd_temp:: Module Security Plan Template + :id: gd_temp__module_security_plan + :status: valid + :complies: std_req__isosae21434__prj_management_6411, std_req__isosae21434__prj_management_6421, std_req__isosae21434__prj_management_6422, std_req__isosae21434__prj_management_6423, std_req__isosae21434__prj_management_6424, std_req__isosae21434__prj_management_6425, std_req__isosae21434__prj_management_6426, std_req__isosae21434__prj_management_6427, std_req__isosae21434__prj_management_6428, std_req__isosae21434__prj_management_6429, std_req__isosae21434__prj_management_64210, std_req__isosae21434__prj_management_64211, std_req__isosae21434__prj_management_6431, std_req__isosae21434__prj_management_6432, std_req__isosae21434__prj_management_6441, std_req__isosae21434__prj_management_6442, std_req__isosae21434__prj_management_6443, std_req__isosae21434__prj_management_6451, std_req__isosae21434__prj_management_6452, std_req__isosae21434__prj_management_6453, std_req__isosae21434__prj_management_6461, std_req__isosae21434__prj_management_6462 + + For the content see here: :need:`doc__module_name_security_plan` diff --git a/process/process_areas/security_management/security_management_concept.rst b/process/process_areas/security_management/security_management_concept.rst index 857a970233..2897a75e2f 100644 --- a/process/process_areas/security_management/security_management_concept.rst +++ b/process/process_areas/security_management/security_management_concept.rst @@ -25,9 +25,6 @@ Concept Description In this section a concept for the Security Management will be discussed. Inputs for this concepts are mainly the requirements of ISO SAE 21434 Clause 5, 6 and 8. -The term security is used here synonymously for the term cybersecurity as defined in ISO SAE 21434. - - Inputs ****** @@ -43,16 +40,19 @@ Stakeholders for the Security Management #. :need:`Project Lead ` - * approving security audit - * planning of development for platform/nodule projects - * status reporting of security activities - * approving security plan, security package + * is overall approver for security management activities. + * For more details refer the role definition in :need:`Project Lead `. #. :need:`Security Manager ` * is the main responsible for the security management work products (as in :doc:`security_management_workproducts`). See also role definition in :doc:`security_management_roles`. +#. :need:`Security Engineer ` + + * is the main responsible for the security management work products (as in :doc:`security_management_workproducts`). + See also role definition in :doc:`security_management_roles`. + #. :need:`Committer ` * creates and maintains SBOM @@ -62,16 +62,17 @@ Stakeholders for the Security Management * reports weaknesses and vulnerabilities -#. :need:`External Auditor ` +#. :need:`External Security Auditor ` * understand activities planning, processes definition and execution (needs review, if we consider that) #. "Distributor" (external role) - * use the platform in a safe and secure way - * integrate the platform in their product (distribution) and security package - * plan this integration (also in time) - * qualify the SW platform as part of his product + * Use the platform in a safe and secure way. + * Integrate the platform in their product (distribution) and security package + * Plan this integration (also in time) + * Qualify the SW platform as part of his product + * Ensures that all Assumptions of use are analyzed for the project. It is recommended that these assumptions of use shall be treated as “requirements” by the the distributors and/or project system integrators. #. :need:`Safety Manager ` @@ -81,22 +82,8 @@ Stakeholders for the Security Management * Supports the creation and maintenance of the SBOM -#. :need:`Quality Manager ` - - * Supports training activities - - -Standard Requirements -===================== - -Also requirements of standards need to be taken into consideration: - -* ISO 26262 -* ASPICE -* ISO SAE 21434 - -Security Management Plans -************************* +Security Plans +************** This SW platform project defines two levels of planning: platform and module. There will be one security plan on platform level and several security plans on module level (one for each module). This is how we organize our development teams and repositories. Each of these security plan "creates" one component OoC. @@ -114,8 +101,8 @@ Apart from the security plans the main work products of security management are Security Management Tooling *************************** -For the security planning and security manual, "re-structured text" will be used for referencing. +For the security planning and security manual a “Docs-as-Code” approach is used and within that approach Id will be used for referencing. -For the activities planning and monitoring (who, when) we use :need:`wp__issue_track_system`. +For the activities planning (who, when) we use :need:`wp__issue_track_system` to create and manage issues, and monitor progress through a project management dashboard. For the reporting (e.g. displaying the status of the work products) additional tooling is created (see :doc:`guidance/security_management_process_reqs`). diff --git a/process/process_areas/security_management/security_management_getstrt.rst b/process/process_areas/security_management/security_management_getstrt.rst index bcc7ffd857..74269b7c23 100644 --- a/process/process_areas/security_management/security_management_getstrt.rst +++ b/process/process_areas/security_management/security_management_getstrt.rst @@ -20,11 +20,25 @@ Getting Started :status: valid :tags: security_management -In case you are appointed as a :need:`Security Manager ` by the -:need:`rl__project_lead` in the development project: - -* Contact the :need:`Project Lead ` (TL) for your Component OoC (Out-of-Context) to establish planning and reporting -* Create your security plan according to :need:`wf__cr_mt_security_plan` -* Make familiar with your role description and the other workflows of security management (see :doc:`security_management_roles` or :doc:`security_management_workflow`) -* Make familiar with the concept :need:`doc_concept__security_management_process` and the :need:`wp__platform_security_plan` -* Make familiar with the development and supporting process descriptions in :ref:`process_description`, especially with the :need:`wp__platform_mgmt` +This document and sub chapters describes the steps needed to be done to ensure compliance to Security according to ISO SAE 21434 (secrity standard used in the project). +This document serves as the entry point or the first document to be read for the Security related processes in this project. +All other sub processes are linked here and in sub chapters. + +General Workflow +**************** +Some workflows/activities have to be done once (or when there is a significant change in project scope) and some have to be executed continuously. +Some workflows have to be done centrally once in the project and some for each modules / sub teams. +All these workflows are defined in the :ref:`workflow_security_management` section. + +Following workflows shall be done centrally or according to the project needs: + +* Create/Maintain Security Plan +* Create/Maintain Security Package +* Create/Maintain Security Manual +* Create/Maintain SBOM +* Monitor/Verify Security + +Some of the workflows are currently either tailored out or not in scope of this project (due to Out-of-Context development). +Refer :need:`wp__tailoring_work_products` section for the details about tailoring. + +.. note:: The term security is used here synonymously for the term cybersecurity as defined in ISO SAE 21434. diff --git a/process/process_areas/security_management/security_management_roles.rst b/process/process_areas/security_management/security_management_roles.rst index 119aee36e1..8c1e8066b5 100644 --- a/process/process_areas/security_management/security_management_roles.rst +++ b/process/process_areas/security_management/security_management_roles.rst @@ -41,16 +41,14 @@ Roles Experience - * 2 years of experience in the management of security topics + * 3 years of experience in the management of security topics * Experience in managing projects * Experience in managing security weaknesses, vulnerabilities Responsibility - * Creates and maintains the Security Plan - * Creates and monitors the completeness of the security package - * Creates and maintains the Security Manual - * Supports creation and maintaining of the SBOM + * Creates and maintains following Security artifcats at platform level: Platform Security Plan, Platform Security package, Platform Security Manual, Platform SBOM + * Approves following Security artifcats at module: Module Security Plan, Module Security package, Module Security Manual, Module SBOM * Verifies, that the preconditions for the "release for production", which are part of the release notes, are fulfilled, and the correctness, completeness and consistency of the release notes * Supports reporting of security related project status * Reports security weaknesses, vulnerabilities @@ -58,7 +56,6 @@ Roles * Plans and approves the security audit (to be discussed, currently not in scope) * Plans and approves the formal security reviews * Approval of security analyses - * Creates and maintains the security manuals on platform and module level * Checks that every person in his team has sufficient security skills for their role Authority @@ -68,3 +65,20 @@ Roles * Recommend the Release of a SW platform or a module * Refusing the approval of work products as defined in the workflows * Refusing the approval of his team's role nomination (i.e. requesting that the role will be withdrawn) + +.. role:: Security External Auditor + :id: rl__security_external_auditor + :status: valid + + Required skills, Knowledge of security standards (ISO 21434), Experience + + * External Auditor comes from organization specialized in secrity audits and assessment, thus sufficient skill should be guaranteed by the sending organization. + * For performing the formal document reviews also a security manager from another Eclipse Safety project can play the role of an external auditor, in this case the same skills apply as for the security manager. + + Responsibility + + * Performing and reporting of secrity audit + + Authority + + * Decision on the passing or failing of an audit diff --git a/process/process_areas/security_management/security_management_workflow.rst b/process/process_areas/security_management/security_management_workflow.rst index 8f08926cf7..49d2b7e73f 100644 --- a/process/process_areas/security_management/security_management_workflow.rst +++ b/process/process_areas/security_management/security_management_workflow.rst @@ -12,6 +12,7 @@ # SPDX-License-Identifier: Apache-2.0 # ******************************************************************************* +.. _workflow_security_management: Security Management Workflows ############################# @@ -53,7 +54,7 @@ For a detailed explanation of workflows and their role within the process model, .. workflow:: Perform Security Audit :id: wf__p_fs_audit_security :status: valid - :responsible: rl__external_auditor + :responsible: rl__security_external_auditor :approved_by: rl__project_lead :supported_by: rl__security_manager, rl__security_engineer :input: wp__module_security_plan, wp__platform_security_plan, wp__module_security_package, wp__platform_security_package @@ -70,12 +71,12 @@ For a detailed explanation of workflows and their role within the process model, .. workflow:: Perform Formal Security Reviews :id: wf__p_formal_security_rv :status: valid - :responsible: rl__external_auditor + :responsible: rl__security_external_auditor :approved_by: rl__project_lead :supported_by: rl__security_manager, rl__security_engineer :input: wp__module_security_plan, wp__platform_security_plan, wp__module_security_package, wp__platform_security_package :output: wp__fdr_reports_security - :contains: gd_guidl__security_plan_definitions, gd_chklst__security_plan, gd_chklst__security_package + :contains: gd_guidl__security_plan_definitions, gd_chklst__platform_security_plan, gd_chklst__platform_security_package, gd_chklst__module_security_plan, gd_chklst__module_security_package :has: doc_concept__security_management_process, doc_getstrt__security_management_process | The external auditor is responsible to perform the formal reviews on Security plan and Security Analysis. @@ -93,7 +94,7 @@ For a detailed explanation of workflows and their role within the process model, :supported_by: rl__committer :input: wp__requirements_feat_aou, wp__requirements_feat, wp__feature_arch, wp__feature_fmea, wp__feature_dfa, wp__requirements_comp_aou, wp__requirements_comp, wp__component_arch, wp__sw_component_fmea, wp__sw_component_dfa :output: wp__platform_security_manual, wp__module_security_manual - :contains: gd_guidl__security_manual, gd_temp__security_manual, gd_guidl__security_plan_definitions + :contains: gd_guidl__security_manual, gd_temp__platform_security_manual, gd_temp__module_security_manual, gd_guidl__security_plan_definitions :has: doc_concept__security_management_process, doc_getstrt__security_management_process | The Security Engineer collects the necessary input for the security manuals on diff --git a/process/process_areas/security_management/security_management_workproducts.rst b/process/process_areas/security_management/security_management_workproducts.rst index e525773ed5..81577b8ffd 100644 --- a/process/process_areas/security_management/security_management_workproducts.rst +++ b/process/process_areas/security_management/security_management_workproducts.rst @@ -14,7 +14,6 @@ Security Management Work Products ################################# - .. workproduct:: Platform Security Plan :id: wp__platform_security_plan :status: valid @@ -27,6 +26,8 @@ Security Management Work Products Guidelines on how an change impact analysis shall be concluded on each item or element involved together with it's connected items or elements. + For the template see here: :need:`doc__platform_security_manual` + This is on following level: * Project/Platform (contains definitions how security planning is performed generally in the project) @@ -41,6 +42,8 @@ Security Management Work Products Guidelines on how an impact analysis shall be concluded on each item or element involved together with it's connected items or elements. + For the template see here: :need:`doc__module_name_security_manual` + This is on following level: * Module (contains activities planning based on a Change Request) @@ -59,7 +62,7 @@ Security Management Work Products :id: wp__module_security_package :status: valid :tags: doc_lifecycle_model_2 - :complies: + :complies: std_wp__isosae21434__prj_management_652 Compiled Security Relevant Work Products. For Module OoC. @@ -75,6 +78,10 @@ Security Management Work Products Will contain formal review report for Security Plan, Security Package, Security Analyses. + For the different review checklist see here: + - Review checklist for Security plans: :need:`doc__platform_name_security_plan_fdr` and :need:`doc__module_name_security_plan_fdr` + - Review checklist for Security packages: :need:`doc__platform_name_security_package_fdr` and :need:`doc__module_name_security_package_fdr` + .. workproduct:: Process Security Audit Report :id: wp__audit_report_security :status: valid @@ -101,6 +108,8 @@ Security Management Work Products This is on platform level. Only one manual for the entire platform. + For template see here: :need:`doc__platform_security_manual` + .. workproduct:: Module Security Manual :id: wp__module_security_manual :status: valid @@ -118,11 +127,13 @@ Security Management Work Products This is on module level. One manual per each module. + For template see here: :need:`doc__module_name_security_manual` + .. workproduct:: Platform Software Bill of Material (SBOM) :id: wp__sw_platform_sbom :status: draft :tags: doc_lifecycle_model_2 - :complies: + :complies: std_wp__isosae21434__continual_8631 Platform Software Bill of Material - comprehensive inventory of software components to ensure security, integrity, and compliance. @@ -131,7 +142,7 @@ Security Management Work Products :id: wp__sw_module_sbom :status: draft :tags: doc_lifecycle_model_2 - :complies: + :complies: std_wp__isosae21434__continual_8631 Module Software Bill of Material - comprehensive inventory of software components to ensure security, integrity, and compliance. diff --git a/process/roles/index.rst b/process/roles/index.rst index 337c694c4b..c1e3cf11ea 100644 --- a/process/roles/index.rst +++ b/process/roles/index.rst @@ -48,6 +48,7 @@ Project Management Roles * High-level project control and coordination between multiple software modules * Escalation instance * Planning and Approval the releases of the + * Approves security related artifcats likes security audit, security plan, security package including status reporting of security activities Authority