Chevron Left
Zurück zu Principles of Secure Coding

Kursteilnehmer-Bewertung und -Feedback für Principles of Secure Coding von University of California, Davis

25 Bewertungen
6 Bewertungen

Über den Kurs

This course introduces you to the principles of secure programming. It begins by discussing the philosophy and principles of secure programming, and then presenting robust programming and the relationship between it and secure programming. We'll go through a detailed example of writing robust code and we'll see many common programming problems and show their connection to writing robust, secure programs in general. We’ll examine eight design principles that govern secure coding and how to apply them to your own work. We’ll discuss how poor design choices drive implementation in coding. We’ll differentiate between informal, formal, and ad hoc coding methods. Throughout, methods for improving the security and robustness of your programs will be emphasized and you will have an opportunity to practice these concepts through various lab activities. A knowledge of the C programming language is helpful, but not required to participate in the lab exercises....


Filtern nach:

1 - 7 von 7 Bewertungen für Principles of Secure Coding

von Sanjeev J

Sep 03, 2019

Matt Bishop is an excellent Secure Coding Trainer. I enjoyed the sessions all the way and it was totally engaging with practical examples.

von Woratham N

Nov 25, 2019

Thanks a lot

von Giorgio B

Oct 28, 2019

Very good overview of Secure Coding principles!

von Howard S

Nov 04, 2019

Good Foundational Learning for secure coding.

von Samantha P C F

Dec 03, 2019


von Tobias A

Oct 13, 2019

Good introduction, at times the explanations are a bit dry and lengthy. A couple more real world stories would spice things up and make principles more memorable.

von Ben

Nov 07, 2019

I felt the scope of this course is too narrow and focussed mainly one a few examples in C code. I would've got more out of it and found it more interesting if the scope was broader and the examples were a higher level, perhaps written in pseudo-code.