Security is most effective when we build it into the software development lifecycle early — and the earlier developers learn how to do this, the more secure our software gets.
We want to train every final-year student and new graduate in New Zealand and Australia who’s aiming for a career in software development.
If you’ve heard the term SBOM floating around, you may have wondered what it is, where it comes from, and how it impacts you in your software development work. We’ll get into all of that, but let’s start with a definition.
We often talk about everyone needing cyber security: from the largest governments to the smallest businesses. We include budgets for it at a national level, and we encourage people through frameworks and regulations. We urge software teams to consider cyber security early and often through every element of the products – building secure systems by design and default.
So, you’ve read the first blog post in our series, about the global move to make software more secure — huzzah! We’re diving into the second one here. Keen to read the third (and last) one too?
The Secure by Design approach features heavily in the guide the Australian government put out together with international government agencies and partners. But what is Secure by Design, and how does this shift in mindset impact your work as a software developer or team lead? Let’s dive in.
Remember when we all realized that the responsibility for our global plastic pollution problem didn’t just lie with the consumer, but also with the manufacturer?
The same is now happening for the tech sector.
This is the first blog post in a three-part series. Keen to read the second and third posts too?
You are a good person. You like to build things and solve problems. It’s not your fault. You also follow the rules. That’s not your fault either.
From our parents to our schooling, from our communities to the laws of the countries we live in – we are taught to behave from a very young age. While we are naturally inquisitive as children, we dial those behaviors down as we age. We remain curious and playful at our core, but we change our behavior in external situations, such as in the workplace, to fit the mold. And it doesn’t stop there.
Hey there, coders, testers, analysts, and software architects — we’ve got something new, just for you.
For the past few years, we’ve made secure development training accessible for more than 5,000 learners and nearly 1,500 organizations worldwide.
Today, we’re so happy to launch our Pro Plan — a new tier of access within SafeStack that’s designed for solo learners who want to level up their secure development skills and earn verified credentials, all with the support of our community.
It seems fitting that I’m writing this blog post in May. Early spring is the season for many exciting things, including some of the world’s most prominent developer and cyber security conferences. Whether you’re a leader in the engineering or security teams, we’re bombarded with new approaches and tools. Vendors are marketing to us, books are released, and conference talks feature throughout our news feeds.
You’re hiring for a new engineering role within your team. Great. You’ve made a shortlist, interviewed a bunch of people, and sent them a coding exercise they need to complete and submit. Now let’s add ChatGPT into the mix. How can we be sure that the code we receive from prospective hires is actually written by them? We can’t. Unless someone writes the code in front of us, there’s no way of knowing.