Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Compliance

PCI DSS Requirement 11 - Changes from v3.2.1 to v4.0 Explained

In the ever-evolving landscape of cybersecurity, staying updated with the latest standards and protocols is crucial. One such standard that has undergone significant changes is the Payment Card Industry Data Security Standard (PCI DSS) Requirement 11. This requirement, focused on the regular testing of security systems and networks, has seen notable updates in its transition from version 3.2.1 to version 4.0.

How to use Vanta and AWS to manage vulnerabilities

This blog is part of a series about how to use Vanta and AWS to simplify your organization’s cloud security. To learn more about how to use Vanta and AWS, watch our Coffee and Compliance on-demand webinar. ‍ Amazon Web Services, or AWS, is one of the most popular cloud providers for organizations today — providing one of the most flexible and secure cloud environments available.

New York Department of Financial Services Rules Part 500: Are You Ready for Amendment 2?

Hackers move fast. The cybersecurity industry works hard to move as fast (or faster) than hackers. And regulators work to keep pace. In 2017, the New York Department of Financial Services enacted the sector’s most ambitious set of cybersecurity regulations: 23 NYCRR Part 500. These “Part 500” rules have been updated to reflect the evolving threat landscape, the most recent change (“Amendment 2”) implemented in December 2023 to address emerging cybersecurity needs.

Post-SOC 2 Gap Analysis: Next Steps for Full Compliance

Achieving SOC 2 compliance demonstrates to customers that your organization takes data security and privacy seriously. The journey to achieve SOC 2 compliance, however, is not easy. For example, when you perform a preliminary assessment to determine your current state of security, you’re likely to find multiple gaps between that current state and what SOC 2 standards expect you to have. You’ll need to close those gaps to achieve full SOC 2 compliance.

What is Compliance in Healthcare: Definition, Regulations, and Solutions

Compliance in healthcare is a critical component to preserving the sanctity of modern society. Compliance in any industry ensures adherence to a minimum set of requirements to ensure quality of service; while undoubtedly important everywhere, it’s more so in healthcare due to its direct impact on human lives. For example, while financial compliance secures the safety of our funds, healthcare compliance ensures the safety of our personal selves.

Enhancing Compliance through Integrated Solutions: A Webinar with #err0 & #BoxyHQ #webinar

The webinar "Enhancing Compliance through Integrated Solutions" by BoxyHQ and err0, moderated by Schalk Neethling, featured insights from Cesar Nicola and Deepak Prabhakara on improving software compliance and security. It focused on the integration of err0's error management with unique codes and BoxyHQ's audit logs for enhanced compliance.

Best Industry Practices for Maintaining SOC 2 Compliance

As data breaches and cyberattacks become more widespread, most businesses are making information security and data privacy a top priority. That means they want to know whether your business can be trusted with their sensitive information. SOC 2 compliance is one of the most effective methods to instill that confidence.

FAQ: What is FIPS 140-2 and "Validated Cryptography"?

As time marches on and technology develops, there’s a constant push and pull between information security and attempts to breach that security. Obscurity – simply hiding from sight – isn’t enough with automated processes capable of scanning any possible address looking for signs of life, so much of modern computer security comes down to cryptography. Pretty much everyone has some experience with cryptography, from our childhood spy media to modern computer science.