You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ALL: As noted in issue #4, I've been working on a course about developing secure software. I suspect many of us agree that knowing how to develop secure software is a best practice :-).
If you're interested in seeing or reviewing the draft contents of this course, please send me an email with a subject line like "Request early access to secure software development course". My email address:
dwheeler AT linuxfoundation DOT org.
I would love to have your feedback/suggestions/etc.
The draft course material is a Google docs document. My plan is to provide "Suggestion" access to people, so that you can directly suggest specific changes (my preference!). If you have broader suggestions that aren't easy to capture that way, create comments.
Our educational folks have asked me to divide up the course. I've divided it into 3 parts:
Secure Software Development - Part I, Fundamentals [Covers basics, requirements, design] - est. 2-4 hours
Secure Software Development - Part II, Implementation - est. 4-6 hours
Secure Software Development - Part III, Verification and Advanced Topics [Covers verification, threat models, cryptography, & other advanced topics] - est. 3-5 hours
Don't take the estimates too seriously, I'm sure things will change anyway.
I stated this in one of the comments in issue #4, but I thought it might be considered "buried"... so I'm creating this separate issue so that anyone who cares will know.
Thank you!
The text was updated successfully, but these errors were encountered:
ALL: As noted in issue #4, I've been working on a course about developing secure software. I suspect many of us agree that knowing how to develop secure software is a best practice :-).
If you're interested in seeing or reviewing the draft contents of this course, please send me an email with a subject line like "Request early access to secure software development course". My email address:
I would love to have your feedback/suggestions/etc.
The draft course material is a Google docs document. My plan is to provide "Suggestion" access to people, so that you can directly suggest specific changes (my preference!). If you have broader suggestions that aren't easy to capture that way, create comments.
Our educational folks have asked me to divide up the course. I've divided it into 3 parts:
Don't take the estimates too seriously, I'm sure things will change anyway.
I stated this in one of the comments in issue #4, but I thought it might be considered "buried"... so I'm creating this separate issue so that anyone who cares will know.
Thank you!
The text was updated successfully, but these errors were encountered: