Memory-safe c and c++ to CERT and MISRA standards
A ready-made course you customise for your organisation, with a live session deck and two surveys. You only add the 7 details that are specific to your organisation.
- Length
- 45 min
- Lessons
- 6 lessons
- Frequency
- At onboarding of C and C++ developers
- Last reviewed
- 21 Oct 2026
A 16-byte buffer receives 40 bytes from a message
Try it: this is one of 17 interactive activities in the course.
What's included
Three pieces that work together
Copy once, get everything. Learners prepare on their own, you answer questions live, and the surveys tell you what stuck.
Self-paced course
Short lessons with real workplace scenarios, not walls of text.
- 6 lessons, about 45 minutes
- Scenario, sorting activity, timeline, tabs and quizzes
Live session deck
An AhaSlides presentation to run after the course, in person or online.
- 10 slides
- Quiz, poll, ranking, word cloud slides
- A closing slide for your contacts
Two surveys
Find out what landed, and whether people use it on the job.
- Post-course feedback, about 2 minutes
- 30-day check-in
- Anonymous by default
- Results feed your next refresher
Learning objectives
At the end of this course, learners can
Each objective and the lesson that covers it.
| ID | Objective | Source | Where it's covered |
|---|---|---|---|
| TO 350.0 | Achieve ≥ 80% on the final assessment | - | Whole course |
| SO 350.1 | Describe stack, heap and object lifetime and what happens when a lifetime ends | Best practice | Whole course |
| SO 350.2 | Use pointers and arrays safely, with bounds checks | SEI CERT C and C++ Coding Standards [check before build] | Whole course |
| SO 350.3 | Recognise common memory-safety flaws: overflow, use after free, double free, leaks | CWE Top 25 (reference) [check before build] | Whole course |
| SO 350.4 | Apply a coding rule set in practice and read a rule violation + your info | MISRA C/C++ (commercial, voluntary) [check before build]; organisation rules | Whole course |
| SO 350.5 | Use static analysis results in code review + your info | Organisation's analysis tool policy | Whole course |
Your part: what a template can't do for you
- Your workplace details: fill in the 7 highlighted fields so the course describes your own policies, contacts and locations.
- Records: record completion in your own LMS or record system.
Course outline
6 lessons, about 45 minutes
Minutes per lesson are an estimate, shared out by page count.
1A crash from one stray pointer
3 pages
9 min
A crash from one stray pointer
3 pages
2Memory layout: stack, heap and lifetimes
3 pages
8 min
Memory layout: stack, heap and lifetimes
3 pages
3Pointers and arrays safely
3 pages
8 min
Pointers and arrays safely
3 pages
4Common memory-safety flaws
3 pages
8 min
Common memory-safety flaws
3 pages
5Coding rules in practice
2 pages
6 min
Coding rules in practice
2 pages
6Static analysis and final assessment
2 pages
6 min
Static analysis and final assessment
2 pages
Live deck and surveys
10 slides to run live, two surveys to close the loop
Pink slides are interactive. Both surveys are anonymous; pink questions are written for this course.
Post-course feedback: 11 questions, about 2 min
- Overall rating 5 stars
- Relevant, realistic, right length, helpful activities agree/disagree grid
- What was most useful? multi-select
- Confidence before this course, and now 1-5 scale
- Confidence in memory layout · pointers · flaws · coding rules · static analysis grid
- Do you run static analysis on every change? multiple choice
- Which memory bug was hardest to find? short text
- I can say ‘I am not sure this pointer is valid’ without feeling judged. 1-5 scale
- One thing we should change or add open text
- Would you recommend this course? NPS
30-day check-in
- Have you used what you learned since the course? multiple choice
- How confident are you today? Compare with day 1 1-5 scale
- Do you know where to find the coding standard and static analysis policy? yes / no / not sure
- A moment where the training helped, or where you weren't sure open text
- Which topics should the next refresher focus on? ranking
Results show whether people use the training on the job, not just whether they finished it.
Make it yours
7 fields to fill in, and you're ready
Everything else is done. These are the details only your organisation knows; each one is highlighted inside the course.
- Link to the C and C++ coding standard in use
{{CODING_STANDARD_LINK}} - Who to ask for help or to report a concern
{{HELP_CONTACT}} - Where completion is recorded
{{LMS_OR_RECORD_SYSTEM}} - Link to the post-course and 30-day survey
{{SURVEY_2_URL}} - Link to the self-paced course
{{COURSE_URL}} - List of approved tools and versions
{{APPROVED_TOOLS}}
Show all 7 fields
- Link to the baseline survey
{{SURVEY_1_URL}}
FAQ
Common questions
Can I run memory-safe c and c++ to CERT and MISRA standards training online?
Yes. The course is self-paced and online, and the live deck lets you add a live session in the room or online.
How often is this training needed?
At onboarding of C and C++ developers, and before a coding standard is adopted.
Who needs this training?
C and C++ developers in embedded, systems and finance teams; run by engineering leads with L&D.
What records should I keep?
Record completion in your own LMS or record system, so you can show who finished the course and when.
Can I edit the content?
Yes, everything. Change the wording, swap scenarios for ones from your workplace, add your logo, or remove parts that don't apply.
Related templates
Often taught together
Using AI coding assistants and agents responsibly
All developers and the team leads · Secure and responsible coding
Secure coding fundamentals: OWASP top 10, input validation and least privilege
Developers on web and back-end teams · Secure and responsible coding
Concurrency safety: Threads, locks and race conditions
Back-end developers and systems engineers · Secure and responsible coding
Ready to run it?
Open the live deck to see how the session runs alongside the course and both surveys.