Security in IT projects: security by design for project managers and Product Owners
Project managers, Product Owners, product teams and business managers · 1 day (7 hours) · in-house, on site or remote
At a glance
- Duration
- 1 jour (7 heures)
- Format
- On site and remote
- Group size
- 12 participants maximum
- Level
- Beginner
- Audience
- IT project managers delivering journeys or applications exposed to external users
- Prerequisites
- No technical background required: the day contains no code, no penetration testing and no tool configuration.
- Methods
- Short talks, each followed by a workshop on the project the participants bring.
- Assessment
- Beforehand: a positioning questionnaire (current projects, data handled, existing relationship with a CISO) that adjusts the examples.
- Lead time
- Scheduled during framing, to suit your availability
- Pricing
- On a quote basis, depending on format, duration and number of participants. The first call is free.
- Accessibility and disability
- See the dedicated section
Security almost always arrives too late in a project: at acceptance testing, when the CISO discovers a journey that has already been built, or after go-live, when a phishing email targets the team. By then, every missed requirement costs a sprint. This day is for the people who frame and prioritise without being security specialists: project managers, Product Owners, business managers. It contains no code and no penetration testing. It builds the framing reflexes that prevent late discovery: naming the assets to protect, writing a security requirement into a user story, deciding who accesses which data, preparing a security acceptance test with the CISO rather than enduring it, and holding your role on the day an incident occurs. The session works on a real project brought by the participants: the requirements and the checklist produced in the workshops are those of that project.
Learning objectives
- Explain why a security requirement discovered at acceptance testing costs more than at framing, and show it on a real project.
- Run a simple risk analysis: list the assets, the plausible threats and the business impacts, then derive three priorities.
- Write a security requirement into a user story and turn it into a verifiable acceptance criterion.
- Map the access rights and sensitive data of a project: who sees what, for how long, with what audit trail.
- Prepare a meeting with the CISO or a security contractor, arriving with the right questions and the right documents.
- Build a security acceptance test: scope, criteria, responsibilities, and what blocks a go-live.
- Hold the project role during an incident: qualify, alert, record, communicate, without standing in for the technical teams.
- Recognise phishing and social engineering as a project risk and set simple rules for the team.
Programme
01Security as a framing requirement
1 hour- Why security gets treated as a final phase, and what that costs when it is discovered at acceptance testing or in production.
- The three moments when a project manager can still act cheaply: the framing note, the backlog, the go-live criteria.
- What security by design means for someone who does not code: questions asked early, not a technical skill.
- Round table: each participant places their project and names their main security worry.
02Simple risk analysis: assets, threats, impacts
1 h 30- Listing the project's assets: data, accounts, journeys, interfaces with partners.
- Identifying plausible threats without an exhaustive catalogue: unauthorised access, leak, tampering, unavailability, impersonation.
- Rating impact in business terms (customers, regulatory obligations, reputation, continuity) rather than in technical vocabulary.
- Deciding: three risks to handle within the project, those you accept, those you escalate.
- Workshop: risk analysis of the project brought in, on a one-page grid, peer-reviewed across sub-groups.
03Writing security into user stories and acceptance criteria
1 h 30- Turning an identified risk into a requirement: authentication, rights, logging, retention, encryption requested from the technical team.
- Writing a security acceptance criterion a business tester can check without a specialised tool.
- Managing access and sensitive data within the project: who sees what, for how long, how it is traced, how an access is removed.
- Data in test and acceptance environments: what never goes there.
- Workshop: rewriting three stories from the project brought in, with their security requirements and criteria.
04Working with the CISO and security contractors
1 hour- What the CISO expects from a project manager, and what they do not: up-to-date documents, recorded decisions, not a technical opinion.
- When to call in a security contractor (audit, penetration test) and how to read their report without being a technician: severity, exploitability, expected fix.
- Weighing a security recommendation against deadline and budget: making it visible at the committee, not burying it.
- Role play: preparing a CISO meeting on the project brought in, with the list of questions and documents to bring.
05Security acceptance testing and go-live preparation
1 hour- What a security acceptance test checks: access, rights, logs, test data, error handling, account recovery journeys.
- Who runs it, on which environment, with which criteria that block the go-live.
- Security reservations in an acceptance report: writing them so that they get followed up.
- Workshop: security acceptance checklist for the project brought in.
06Incident, phishing and social engineering: the project's role
1 hour- Qualifying an incident from the project side: what is a defect, what is a security incident, who it goes to and how fast.
- Holding your role during the incident: recording the facts, feeding communication, protecting decisions, not improvising a fix.
- Phishing and social engineering: why a project team is a target (contractors, temporary access, schedule pressure) and the three rules that hold.
- Validation quiz, corrected in the room, and individual two-week action plan.
Who it is for
- IT project managers delivering journeys or applications exposed to external users
- Product Owners and product teams whose backlog contains personal data or payment data
- Business managers who own a digital project and answer for its data
- PMOs and portfolio managers who want a shared grid of security questions at framing
- Teams working with a CISO or a security contractor without knowing what to ask them, or when
What you take away
- The one-page risk analysis of your project: assets, threats, impacts, three priorities.
- Three user stories from your backlog rewritten with their security requirements and acceptance criteria.
- A map of the project's access rights and sensitive data.
- The list of questions and documents to bring to a meeting with the CISO.
- A security acceptance checklist, with its go-live blocking criteria.
- A one-page reflex sheet for incident day: qualify, alert, record, communicate.
- Blank templates for these documents and the day's material.
Prerequisites
- No technical background required: the day contains no code, no penetration testing and no tool configuration.
- Having taken part in at least one IT project, in any capacity.
- Bringing a real project, current or upcoming: it is the material for the risk analysis and requirement-writing workshops.
Teaching methods
- Short talks, each followed by a workshop on the project the participants bring.
- One-page grids filled in during the session: risk analysis, requirements, acceptance checklist.
- Sub-groups of three to four participants, with peer review of what each produces.
- Role play: preparing a meeting with the CISO, one participant holding that role.
- Field stories from projects under KYC and GDPR constraints: what was asked, what blocked, what was traded off.
- No security tool is handled: everything is done in a spreadsheet or in your backlog tool.
Assessment of learning
- Beforehand: a positioning questionnaire (current projects, data handled, existing relationship with a CISO) that adjusts the examples.
- During the session: the risk analysis and the three rewritten stories are assessed against a grid handed out at the opening (named assets, plausible threat, verifiable requirement).
- The CISO meeting role play is debriefed against three criteria: questions prepared, documents brought, decision to be made identified.
- At the end: a validation quiz covering the six modules, corrected and discussed in the room.
- A few weeks later: a remote check-in, outside training hours, on what was added to the project's backlog and acceptance plan.
Where what I teach comes from
Adrien Bouthet, freelance IT project manager and Product Owner based in Bordeaux, eight years on exposed digital projects. I am not a technical security specialist: I am a project manager who learnt to handle security at framing because there was no alternative. Since February 2025 I have been steering the digital onboarding journeys at La Banque Postale (account opening, minor and adult journeys, Livret A subscription), with two external partnerships integrated through APIs, under permanent KYC and GDPR constraints, with fewer than three production incidents per year as the result. That practice feeds the workshops of this day: risk analysis, requirements written into stories, security acceptance. Those figures are results from steering assignments, not a promise made to participants. I also hold the Cyber Security Foundation certification (CertiProf, 2021), which gives a shared vocabulary with a CISO without making me an auditor, and I have been teaching in schools since 2020.
Real example
The examples of this day draw on my experience of La Banque Postale's digital onboarding journeys: journeys exposed to external users, two partnerships integrated through APIs, permanent KYC and GDPR constraints, and fewer than three production incidents per year. An assignment result, not a promise made to participants.
Read the case studyFrequently asked questions
Is this a technical course? Will we do penetration testing or code?+
No. The day contains no code, no penetration testing and no handling of security tools. It is for the people who frame, prioritise and run acceptance testing. Technical security audits remain the job of specialised contractors: the session teaches you to bring them in at the right time and read their report, not to do their work.
Our company already has a CISO. Why train the project managers?+
Because the CISO cannot sit in every framing workshop or review every story. When the project reaches them with named assets, written requirements and recorded decisions, their intervention takes an hour instead of a week. The day builds exactly that entry file.
Do we work on our own projects?+
Yes. Each participant comes with a real project, current or upcoming. The risk analysis, rewritten stories and acceptance checklist produced during the day are those of that project. Nothing is kept after the session, and real data is never needed: the examples work on the structure of the project, not its contents.
On site or remote?+
Both. On site at your premises, in Bordeaux and across Nouvelle-Aquitaine, or remotely anywhere in France, with the same sub-group workshops and the same CISO meeting role play. A mixed format is possible when part of the team sits on another site.
How many participants at most?+
Twelve. Beyond that, peer review of the risk analyses no longer fits in the day and the role play loses its point. Below four, sub-groups make no sense: the format becomes a shorter workshop, to be defined together.
Does the day cover GDPR?+
It crosses it without covering it: personal data is an asset like any other in the risk analysis, and data retention appears in the requirements. The legal framework of GDPR, records of processing and impact assessments are not on the programme and belong to specialised advice.
How does it relate to the 'Steering an IT project end to end' course?+
It extends it. The two-day course sets out the full mechanics of steering; this day revisits three of its moments (framing, backlog, acceptance testing) from the security angle. The two can be taken in either order, and the templates are compatible.
Framework and terms
Funding
These sessions are invoiced directly to the company, out of its own skills development budget. They are not eligible for pooled funding schemes (OPCO, CPF, France Travail), which require Qualiopi certification.
Certification
This session is not a certifying course. I do not deliver any Scrum.org, Scrum Alliance, Scaled Agile (SAFe) or PeopleCert (ITIL) certification, nor any qualification registered with the RNCP or the Répertoire spécifique. The goal is operational: practices you can apply, not a diploma.
Contractual framework
Each session is covered by a professional training agreement (convention de formation professionnelle) signed before the start, setting out the objectives, the programme, the duration, the delivery arrangements and the agreed fee. The internal rules applicable to the session are handed to participants at the opening.
Certificate of attendance
A certificate of completion is handed to each participant at the end of the session. It states the objectives, the nature and the duration of the training, along with the results of the assessment of learning.
Accessibility and disability
Disability referent: Adrien Bouthet, contact@adrienbouthet.fr. Any situation requiring an adjustment (access to the premises, adaptation of the materials, of the pace or of the assessment arrangements) is examined during the framing phase, within 5 working days. If the adjustment exceeds our means, we refer to specialised resources (Agefiph, Cap emploi).
A project team to train in security
Book a free first call. We look at your current projects, pick the one that will serve as workshop material, and set the date.
The matching service
Freelance IT project manager