Where does the responsibility for code vulnerabilities lie, and how can cybersecurity leaders address these vulnerabilities? Find tools for determining the security of code and mitigating cyber risk in your organization.

A multi-use commercial and residential building will be secured by an access control and visitor management system from AMAG Technology and West Fire Systems. Read more about the tools used in this security case study.

Business leaders need security solutions that adapt to their environment and build off of the foundations they’ve set. New research from Johnson Controls highlights key areas of change that security executives can monitor.

A new report from Veriff analyzes data about the cybersecurity workforce, finding strong cybersecurity industries in the United States, Brazil and Mexico. The report also details which jobs are the most in-demand, having researched global job boards and roles at cybersecurity companies.

A more foundational goal is to make security and compliance part of the development process from the start. This is a transition that requires DevOps to bring along risk, security and compliance teams into the shared responsibility of making the organization resilient to change. But bringing the idea of shared responsibility to fruition can be difficult because there is a natural tension between DevOps and SecOps, as they have different charters and cultures. DevOps can be seen as more of a do culture (Atlassian calls this a “do-ocracy”) and SecOps can be seen as a control culture and they are inherently in conflict. To fulfill the promise of teaming for shared responsibility, DevOps and SecOps should align on three key objectives: collaboration, communication and integration.

Enterprises will face nine major threats, including vulnerabilities in software and other applications, state-backed espionage with emerging technology and malware feats and manipulated machine learning, says Threat Horizon 2021 from the Information Security Forum (ISF).