This website requires certain cookies to work and uses other cookies to help you have the best experience. By visiting this website, certain cookies have already been set, which you may delete and block. By closing this message or continuing to use our site, you agree to the use of cookies. Visit our updated privacy and cookie policy to learn more.
This Website Uses Cookies By closing this message or continuing to use our site, you agree to our cookie policy. Learn MoreThis website requires certain cookies to work and uses other cookies to help you have the best experience. By visiting this website, certain cookies have already been set, which you may delete and block. By closing this message or continuing to use our site, you agree to the use of cookies. Visit our updated privacy and cookie policy to learn more.
The massive Kaseya security breach that impacted thousands forced the industry to re-evaluate their software supply chain security practices. Here we break down the cybersecurity lessons that still need to be learned.
The Okta, GitHub and MailChimp supply chain breaches illustrate the inherent risks of leaving your supply chain in the dark. What can be done to mitigate these risks?
Any comprehensive approach to cybersecurity must include a detailed third-party risk assessment, covering an assessment of how partners view governance, risk, and compliance within their own organizations.
Given the increase of attacks on critical infrastructure and third-party suppliers and supply chain partners, let's address security concerns for supply chains and quick solutions.
Chief information security officers (CISOs) are grappling with a wide range of risks and challenges, especially with cloud-based applications and Application Programming Interfaces (APIs).
Among ransomware, software supply chain attacks and data breaches, a Blumira report found that identity-based attacks are the top threat organizations faced in 2021.