Some developers love to create crafty code, others utilize strange code bases or off-the-reservation services, all of which creates a running battle with cybersecurity teams trying to protect the business and users. Here’s how both can coexist in relative peace with a good balance between features and security.

Regardless of whether developers are building a Windows or Linux application, a mobile app, cloud service, chatbot, docker utility or progressive web app, great risks are often, sometimes unknowingly, being taken.

Cybersecurity teams know it can take just one weakness across the application or any service it touches to make the business or its customers vulnerable to hackers and their army of automated tools.

The risks come into play regardless of the history of the coding team. From rockstar developers to fresh-out-of-college graduates, missing one port reference, ignoring one internal rule or borrowing one dubious codelet that solves a problem can wreak havoc on the business.

Let’s Be Coding Friends

Both sides of the equation are under pressure, business leaders want their coders to churn out apps and tools to use or sell yesterday. That’s as cybersecurity teams are tasked with being as invisible and frictionless as possible, while protecting everyone from the armies of darkness beyond the firewall.

The key to success is clarity of message and a well-defined plan for each project. Security must play an equal part of the quality checklist that any project goes through. Many code shops are moving to the DevOps model, where modular, goal-based milestones mark the lifecycle of the project.

In tandem with agile development, they help move projects rapidly, but within a structurally-defined process for quality, goal-meeting and feature management. Add security to that list and a business can proceed to develop apps that meet all the company’s security requirements, tested for integrity and meet any industry or governmental standards.

To achieve this, both heads of security and the development teams need to be on the same page, highlighting the security-as-quality message. By building in security checks, code validation and training all developers in the aspects of vulnerabilities, along with regular check-ins along the way to completion, a secure outcome for the application is guaranteed.

Every Business Needs a Security Master

An increasingly common role in larger enterprises is a chief digital/information security officer (or similar). In any smaller business, someone suitably qualified needs to take on that role and be responsible for the reporting, cataloguing and management of security solutions, risks and flaws.

That person is an ideal focal point for getting the development teams in line with the security needs of the business. This person can be one of the development team, and with responsibility for any future issues is more likely to police the team’s efforts. To help build a strong bond between the two, when launching and development project, teams must follow the ground rules set by the security team.

The Rules of the Coding Road

Training lessons or days that highlight the need for security, what happens when it is ignored, and highlight the main and minor flaws in coding techniques that lead to hacks will help alert the developers to the risks, and highlight the issues.

Code bounties and rewards can help encourage developers to spot flaws across the project code base, and any business should offer company-wide training in spotting hacks, flaws and other ways that hackers could access native code.

These guidelines along with strong rules on “borrowed” code, use of outside services and other likely weakpoints will see any business develop stronger, secure applications.