Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Compliance

CIS Control Compliance and Centralized Log Management

Your senior leadership started stressing out about data breaches. It’s not that they haven’t worried before, but they’ve also started looking at the rising tide of data breach awareness. Specifically, they’re starting to see more new security and privacy laws passed at the state and federal levels. Now, you’ve been tasked with the very unenviable job of choosing a compliance framework, and you’re looking at the Center for Internet Security (CIS) Controls.

GDPR Compliance: The Critical Role of Data Protection Officers

The General Data Protection Regulation (GDPR) is a comprehensive data protection law covering the European Union (EU) and is widely regarded as one of the world’s strictest privacy regulations. The GDPR unifies data regulation within the EU and provides individuals control over their personal data. The GDPR includes information about Data Protection Officers (DPOs).

CrowdStrike Launches SEC Readiness Services to Prepare Boardrooms for New Regulations

CrowdStrike is today debuting CrowdStrike SEC Readiness Services to guide organizations along the path to compliance as they navigate the new SEC cybersecurity disclosure rules. These services, powered by the AI-native CrowdStrike Falcon® XDR platform and industry-leading CrowdStrike Services team, give customers the insight they need to harden defenses, make materiality decisions and navigate the annual disclosure process with confidence.

Test and evaluate your WAF before hackers

Since 1991, Web Application Firewall, commonly referred to as WAF, has become one of the most common application security technologies available on the market. Since the last century, WAFs have evolved by incorporating the cloud and using Machine Learning instead of RegExp. Currently, few technologies, such as NG-WAF, RASP, WAAP, and a few others, have internal WAF capabilities, which prevent web applications and API threats.

Ensuring PCI DSS 4.0 Compliance with Feroot: A Deep Dive into Requirement 6.4.3

The Payment Card Industry Data Security Standard (PCI DSS) 4.0, issued a comprehensive set of requirements, to safeguard online payment systems against breaches and theft of cardholder data. Requirement 6.4.3 is one of the critical components for businesses that take online payment and focuses on the management and integrity of scripts on webpages that take payment card (i.e.m credit card) payments.

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.