Securing Software Development – Free ISC2 Virtual Event

[AndreaMoore]

Maintaining strong security practices requires staying in front of changes and accepting challenges that can impact every phase of the software development lifecycle – from design to disposal and everything in between.

Join us for ISC2 Spotlight: Secure Software Development, a virtual deep dive into securing applications from start to finish. Whether you are involved in software design and implementation, or testing and development, this event will provide timely take-aways and best practices that you can implement in your organization.

The virtual two-day event, which includes Q&A with presenters moderated by Brandon Dunlap, takes place November 8-9. ISC2 members, associates and candidates can attendee for free and earn 5.5 CPE (Continuing Professional Education) credits. This is the last of highly-rated Spotlight events this year, so don’t miss out!

Everyone is encouraged to register as only registered attendees will be able to view the recordings to earn CPE credits after the live event is complete. Live attendees will earn the CPE credits automatically which will post to their ISC2 member accounts within two weeks.

Register now to secure your spot and earn 5.5 CPE credits!

[Early_Adopter]

This is a goodie especially for our new CC Members looking to break into cybersecurity. Because of the trade-off that is software development that produce managers/owners and others make it’s potentially really hard to do the right thing when developing software - the more shortcuts taken in code, the more vulnerable OSS and commercial components with vulnerabilities accepted as excepted the harder it becomes to cover the codebase - this can have a corrupting affect on the dev team culture, and then you can’t move easily because you’re years behind and the application doesn’t work on the new codebase. All because of the human urge to mask bad decisions and people in charge to not be accountable - learn the principles here well - read the OWASP, and always as the first thing you do patch and update and make your codebase robust to the challenges of update and you can be quite the asset to the development team, SRE, DevOps tool chain priesthood(bless this Jenkins that it may smoothly deploy, and let not our instances be as unto kittens, but rather alike with the stoic cattle…). You’ll need to learn to code, but there’s good knowledge here.

[Gazelle]

Looking forward to it!