Roles#

Security Manager
status: draft

The Security Manager is responsible for making sure that ISO SAE 21434 is complied to in the project. The Security Manager shall lead and monitor the security relevant activities of the project.

Required skills

  • Degree: Master’s degree in electrical engineering/computer science/mathematics, or similar degree, or comparable work experience

  • Solid understanding of security management

  • Knowledge in project management

  • Deep understanding of quality criteria and the correlating methods and procedures to achieve and verify them

  • Technical know-how of embedded systems

  • Preferred training: (Automotive) Cybersecurity Specialist (CySec) or similar

Knowledge of standards

  • ISO SAE 21434

Experience

  • 2 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

  • 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

  • Coaches the project team w.r.t all questions related to security

  • 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

  • Escalation of planning topics to the project manager defined in the security plan

  • Initiate the publication of a security weakness, vulnerability

  • 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)