IT project security training

Build cybersecurity in from the scoping stage and at every step of your projects. Learn to identify risks, involve the right people and anticipate security requirements, to avoid delays, extra costs and last-minute fixes.

GRC-120 · Foundation · 1 day · 15 participants max. · Guided project case

Why build security into IT projects?

A security requirement identified too late can lead to delays, extra costs or the reversal of choices already made. Building cybersecurity in from the scoping stage makes it possible instead to anticipate risks and take the right decisions before they become costly to correct.

This course helps you adopt a practical Security by Design approach: assess what is at stake from the very first decisions, analyse the risks of the target solution, define the right requirements and check they are met throughout the project lifecycle.

Designed for project managers, Product Owners and governance stakeholders, it gives simple markers for knowing when to call on the security teams, what information to give them and which controls to anticipate, with no prior technical expertise in cybersecurity.

Through field examples, a live hacking demonstration and a guided project case, you will develop a reusable method for building security into Agile approaches as well as more traditional lifecycles.

Project · customer portalSecurity by DesignScopingDesignBuildTestingGo-livequalificationrisk analysisrequirements approvedpentestQualification sheetscopingExposureInternetDatapersonal (FADP)CriticalityhighCLOSER SECURITYATTENTION

On the programme

  • Security by Design
  • Agile
  • V-model
  • Risk analysis

What you will be able to put into practice

By the end of the course, you will be able to:

  • Integrate

    security from the scoping stage to reduce risks, delays and the cost of fixes late in the cycle.

  • Spot

    the projects that need closer security attention, based on their exposure, their criticality, the data processed and the characteristics of the solution.

  • Involve

    the right people at the right time, giving the security teams the information they need to speed up decisions and approvals.

  • Integrate

    risk analysis into project steering to assess confidentiality, integrity, availability and compliance issues.

  • Anticipate

    security requirements and controls ahead of the testing, audit, pentest, approval and go-live phases.

  • Adopt

    simple, practical reflexes to build security into Agile projects as well as traditional approaches for good.

The format in practice

Duration

1 day

1 day · 8 hours

Group size

15 max.

15 participants max.

Format

  • Focused input
  • Live hacking demonstration
  • Guided project case
  • Field exchange

Prerequisites

  • Experience managing or contributing to projects recommended
  • No prior knowledge of cybersecurity required
GRC-120FoundationIT project security

Certification

Certificate of attendance

Each participant receives this digital badge in their name, level 1 of 3 in the GRC series.

Assessment

  • Final project case: assessing what is at stake, identifying risks and defining the first security requirements

Who it is for

  • Project managers
  • Product Owners
  • PMOs
  • Business managers
  • Governance and project lifecycle stakeholders

Methods

  • Field examples
  • Live hacking demonstration
  • Guided project case
  • Exchange between participants

Materials

  • Course materials
  • Quick-reference sheets
  • Qualification template
  • Security requirements table

Practice

  • Governance
  • Project security
  • Security by Design

Build security into your projects from the very first decisions

Let's design a course around your project management methods, your governance and the situations your teams face, to make Security by Design an operational reflex.