CodeSecCon Brings Developers and Security Teams Together to Fix a Growing Blind Spot
A virtual conference focused on building safer software is drawing both coders and cybersecurity professionals to the same table, a pairing that rarely happens and badly needs to.
Key points
- CodeSecCon is a free virtual event aimed at closing the gap between software developers and cybersecurity professionals.
- The conference focuses on application security, meaning the practice of finding and fixing weaknesses in software before attackers can use them.
- SecurityWeek highlighted the event as part of broader industry efforts to push security earlier into the software-building process.
- Developers and security teams historically work in separate silos, a split that leaves software riddled with preventable flaws.
Most software is written with speed in mind, not safety. Deadlines come first. Security checks, when they happen at all, get bolted on at the end, and by then fixing problems costs far more time and money than catching them early would have.
CodeSecCon is a virtual conference designed to fix that habit.
What is this event actually about?
CodeSecCon gathers software developers and cybersecurity professionals in the same online space to talk about application security, which is the discipline of spotting and closing weaknesses in software before criminals find them. The goal is practical: give developers the tools and thinking they need to write safer code from the first line, not the last.
Application security matters to ordinary people because the apps they use every day, banking, healthcare, travel booking, run on code. A flaw in that code can expose passwords, medical records, or payment details.
Why does the developer-security split cause problems?
The gap is real. Developers are trained to build features. Security teams are trained to break things and find flaws. Both groups are usually under pressure, and they rarely sit in the same room long enough to share what they know.
When security comes late in the process, fixing a single flaw can require rewriting large chunks of code, delaying releases and burning budget. Research from the National Institute of Standards and Technology has long shown that flaws caught during design cost roughly thirty times less to fix than those caught after release.
Conferences like CodeSecCon exist specifically to close that gap, putting both groups in conversation before the damage is done.
What should ordinary people take from this?
You do not need to write code to care about this. Every app you trust with personal information depends on decisions made by developers, often under time pressure, often without security training.
Events that bring security thinking into the development process earlier mean the software that runs your life gets a little harder for criminals to break. That is worth paying attention to, even from a distance.
If you work in an organisation that builds software, even simple internal tools, asking your development team how security is handled during the build process, not after, is a reasonable and worthwhile question.
