diff --git a/slides/debugging-application-debugging/debugging-application-debugging.tex b/slides/debugging-application-debugging/debugging-application-debugging.tex
index 48b39b4ee9..6782473a3f 100644
--- a/slides/debugging-application-debugging/debugging-application-debugging.tex
+++ b/slides/debugging-application-debugging/debugging-application-debugging.tex
@@ -18,6 +18,12 @@ \subsection{Good practices}
       \item GCC allows to do so using the \href{https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gcc/Static-Analyzer-Options.html}{-fanalyzer} flag
       \item LLVM provides \href{https://clang-analyzer.llvm.org/command-line.html}{dedicated tools} that can be used in build process
     \end{itemize}
+    \item You can also enable component-specific helpers/hardening
+    \begin{itemize}
+      \item If you are using the GNU C library, you can for example enable
+            \href{https://www.gnu.org/software/libc/manual/html_node/Source-Fortification.html}{\_FORTIFY\_SOURCE}
+            macro to add runtime checks on inputs (e.g: buffers)
+    \end{itemize}
   \end{itemize}
 \end{frame}